perf: check validity before constructing a new set of requirements

[tzneal]

Description
When checking if a Pod will work on an existing Node, we validate in several ways including
checking the Pods requirements vs the Node's requirements. If it fails at any step,
we need to leave the Node's requirements unchanged. Previously we were:

1. Creating set of temporary requirements from the current node's requirements
2. Check if the Pod is compatible with them
3. Assigning those back to the Node if all compatibility checks passed

This changes the order so that we check for compatibility with the Pod first so that
in the case of a Pod not being compatible, we can avoid the allocation that occurs when
creating the temporary set of requirements.

How was this change tested?

Unit testing & deployed

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[coveralls]

Pull Request Test Coverage Report for Build 13420882534

Details

• 2 of 2 (100.0%) changed or added relevant lines in 1 file are covered.
• 7 unchanged lines in 2 files lost coverage.
• Overall coverage decreased (-0.05%) to 81.429%

---

Files with Coverage Reduction	New Missed Lines	%
pkg/controllers/provisioning/scheduling/nodeclaim.go	3	86.98%
pkg/controllers/disruption/consolidation.go	4	88.55%

Totals
Change from base Build 13378807880:	-0.05%
Covered Lines:	9243
Relevant Lines:	11351

---

💛 - Coveralls

[jonathan-innis]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jonathan-innis, tzneal

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [jonathan-innis,tzneal]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment