fix: Ensure that resource limits that exactly equal capacity are allowed

[willthames]

Fixes #198

Description
Change the definition of ExceededBy to allow exact resource matches (this can happen if a Provisioner has
spec.resources.limits.cpu set to a value identical to a node's CPU count (or a multiple of a node's CPU count))

How was this change tested?

I wasn't able to find an existing test suite that handled node provisioning (I did find a pod provisioning suite but couldn't write a test that would fail before this change and would work after this change). i.e. this change is as yet untested

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

[sftim]

AIUI, this can happen even without:

spec.resources.limits.cpu set to a value identical to a node's CPU count (or a multiple of a node's CPU count))

For example: eligible nodes come in sizes of 12, 20, 32 or 40 CPUs, and the limit is set to 112 CPU. That should be able to be reached exactly even though the limit isn't a multiple of any eligible node's CPU count.

[jonathan-innis]

@willthames Do you mind adding a unit test alongside your change to catch this in the future?

[jonathan-innis]

Otherwise, LGTM! 🚀

[coveralls]

Pull Request Test Coverage Report for Build 4079333176

• 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
• 12 unchanged lines in 2 files lost coverage.
• Overall coverage remained the same at 78.355%

---

Files with Coverage Reduction	New Missed Lines	%
pkg/controllers/deprovisioning/controller.go	3	76.54%
pkg/controllers/deprovisioning/events/events.go	9	80.0%

Totals
Change from base Build 4069455737:	0.0%
Covered Lines:	6219
Relevant Lines:	7937

---

💛 - Coveralls

[jonathan-innis]

LGTM 🚀