test: Fix scale test provisioning spike

[jigisha620]

Fixes #N/A

Description We have been seeing spikes in the scale tests for provisioning. That's because there are two different tests that are captured by the same metric and the execution times are different for both.

1. Metric node-dense for node dense scale-up and node dense scale-up with minValues
2. Metric pod-dense for pod dense scale-up and pod dense scale-up with minValues

Created a different metric for scale up with and without min values. Now we have node-dense, node-dense-min-val, pod-dense, pod-dense-min-val.

How was this change tested?

Does this change impact docs?

• [ ] Yes, PR includes docs updates
• [ ] Yes, issue opened: #
• [x] No

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

[netlify[bot]]

✅ Deploy Preview for karpenter-docs-prod canceled.

Name	Link
🔨 Latest commit	fe3ced493df193794fe93ef46dbf6766fa18cd3a
🔍 Latest deploy log	https://app.netlify.com/sites/karpenter-docs-prod/deploys/6670b865ef56690009d74c4d

[coveralls]

Pull Request Test Coverage Report for Build 9555675267

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage decreased (-0.01%) to 82.467%

---

Files with Coverage Reduction	New Missed Lines	%
pkg/providers/amifamily/ami.go	1	90.56%
<!--	Total:	1		-->

Totals
Change from base Build 9543745280:	-0.01%
Covered Lines:	5550
Relevant Lines:	6730

---

💛 - Coveralls