fix: Cache Instance Types for both AWSNodeTemplate and EC2NodeClass

[engedaam]

Fixes #5578

Description
When a AWSNodeTemplate and EC2NodeClass are contain identical values in the configurations, Karpenter would treat the set of instance types as the same even if they have different requirements. This is a problem as the v1beta1 well-known labels and v1alpha5 well-known labels have a one label difference in that being karpenter.k8s.aws/instance-pods. So if the cached instance types were from a AWSNodeTemplate would have karpenter.k8s.aws/instance-pods in the requirement set for its list of instancetypes, which will result in a Compatibility check with NodeClaims invalid for all the instancetypes. This will prevent Karpenter from launching any nodes.

How was this change tested?

• Manually tested

Does this change impact docs?

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

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

[jonathan-innis]

LGTM 🚀

[coveralls]

Pull Request Test Coverage Report for Build 7823255847

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

---

Totals
Change from base Build 7719733856:	0.0%
Covered Lines:	6175
Relevant Lines:	7498

---

💛 - Coveralls