generic-cluster-provider.ts: specifying a launchTemplate in ManagedNodeGroup causes amiType and amiReleaseVersion to be ignored/discarded

[OK-Apps]

Describe the bug

when specifying a launchTemplate in ManagedNodeGroup properties - it causes the specified amiType and amiReleaseVersion to be ignored/discarded -
i.e. the AmiType and ReleaseVersion disappear from the CloudFormation template that is being generated

Expected Behavior

adding a launchTemplate to ManagedNodeGroup properties does not cause ignoring/discarding amiType and amiReleaseVersion properies - i.e. respective AmiType and ReleaseVersion CloudFormaton properties are not disappearing from the CloudFormation template that is being generated

Current Behavior

when specifying a launchTemplate in ManagedNodeGroup properties - it causes the specifiedamiType and amiReleaseVersion to be ignored/discarded -
i.e. the AmiType and ReleaseVersion disappear from the CloudFormation template that is being generated

Reproduction Steps

Step 1.
first generate (synth) with using ManagedNodeGroup without launchTemplate and see that CloudFormation template contains AmiType and ReleaseVersion with correct values (as specified by amiType and amiReleaseVersion props)

const managedNodegroup1:blueprints.ManagedNodeGroup = {
  id: idForManagedNodegroup1,
  amiType: eks.NodegroupAmiType.AL2_X86_64,
  amiReleaseVersion: amiReleaseVersion,         
  instanceTypes: [new ec2.InstanceType(instanceType)], 
  nodeGroupCapacityType: eks.CapacityType.ON_DEMAND,  
  desiredSize: nodegroupDesiredSize,
  minSize: nodegroupMinSize,
  maxSize: nodegroupMaxSize, 
  nodeGroupSubnets: vpcSubnetsSubsetSelected,
  nodeRole: iamRoleForEksNodegroupWorkerNodes, 
};

Step 2.
now,
add a launchTemplate as well and synth again and see that AmiType and ReleaseVersion completely disappeared from the CloudFormation template:

const managedNodegroup1:blueprints.ManagedNodeGroup = {
  id: idForManagedNodegroup1,
  amiType: eks.NodegroupAmiType.AL2_X86_64,
  amiReleaseVersion: amiReleaseVersion,         
  instanceTypes: [new ec2.InstanceType(instanceType)], 
  nodeGroupCapacityType: eks.CapacityType.ON_DEMAND,  
  desiredSize: nodegroupDesiredSize,
  minSize: nodegroupMinSize,
  maxSize: nodegroupMaxSize, 
  nodeGroupSubnets: vpcSubnetsSubsetSelected,
  nodeRole: iamRoleForEksNodegroupWorkerNodes,
  launchTemplate: {
       // "You can pass Custom Tags to Launch Templates which gets propagated to worker nodes."
       tags: {
           "Name": `by nodegroup ${idForManagedNodegroup1}`,
       }
   }
};

Possible Solution

No response

Additional Information/Context

these lines might be related to it:
https://github.com/aws-quickstart/cdk-eks-blueprints/blame/ca3e9871abbcbce0d478924c44bbdb2d8ebe90bf/lib/cluster-providers/generic-cluster-provider.ts#L397

CDK CLI Version

2.86.0 (build 1130fab)

EKS Blueprints Version

1.10.0

Node.js Version

v18.12.1

Environment details (OS name and version, etc.)

amazonlinux 2023

Other information

No response