user-scheduler: tweak modern configuration

[consideRatio]

This is a followup on #1778 which didn't ensure that pods are scheduled on the most used node correctly because there were some remnant competing logic. This PR disables the competition tothe primary logic we want to dictate the scheduling in the NodeResourcesMostAllocated plugin.

See #1778 (comment) for a discussion on this PR.

As this PR is a complementary fix to #1778 recently merged, I'll go ahead and merge this directly if tests succeeds.

[consideRatio]

Tested to have worked out well on k8s 1.17 woop woop! 🎉 Now no scheduler plugin influence the node-scoring to disrupt the important plugin: NodeResourcesMostAllocated.

InterPodAffinity            scores on pod1 => [{node1 0} {node2 0}]
NodeAffinity                scores on pod1 => [{node1 0} {node2 0}]
NodePreferAvoidPods         scores on pod1 => [{node1 1000000} {node2 1000000}]
PodTopologySpread           scores on pod1 => [{node1 200} {node2 200}]
TaintToleration             scores on pod1 => [{node1 0} {node2 100}]
NodeResourcesMostAllocated  scores on pod1 => [{node1 8} {node2 55}]