feat: Extend more control over Karpenter permissions for 0.32+ changes

[bryantbiggs]

What does this PR do?

• Extend more control over Karpenter permissions for 0.32+ changes
• Remove the doubly redundant !var.karpenter_enable_instance_profile_creation conditional on the Karpenter instance profile

Motivation

• With this change, users now have the ability to change the permissions used by the Karpenter IRSA to something like:

module "eks_blueprints_addons" {
  source = "aws-ia/eks-blueprints-addons/aws"
  
  ...
  enable_karpenter = true
  karpenter = {
    irsa_tag_key   = "aws:ResourceTag/karpenter.sh/nodepool"
    irsa_tag_value = "*" 
  }
}

• This change also extends the current value patterns for the Name tag value to include *ec2.internal which has been reported as another common name pattern
• The instance profile changes is meant to support users migrating from <= 0.31 to 0.32+ where Karpenter starts creating the instance profile that it will use. This change allows the current instance profile to stay around longer until users decide its safe to remove by using:

module "eks_blueprints_addons" {
  source = "aws-ia/eks-blueprints-addons/aws"
  
  ...
  enable_karpenter = true
  karpenter_node = {
    create_instance_profile = false
  }
}

• Resolves Karpenter: panic  #299
• Resolves Karpenter - Reconciliation not possible for custom named instances #300
• Resolves Karpenter Instance Profile broken since 1.9.2 #304
• Resolves Karpenter name tags are incorrect? #309

More

• Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
• Yes, I ran pre-commit run -a with this PR

For Moderators

• E2E Test successfully complete before merge?

Additional Notes

[rodrigobersa]

LGTM