1. Proposed title of this feature request
Enable customization of idle connection tracking timeout for EC2 instances in ROSA

2. What is the nature and description of the request?
Previous generations of AWS EC2 instances used a default idle connection tracking timeout of 432,000 seconds. With the introduction of Nitro v6 instances, this default was reduced to 350 seconds, while still allowing customization within a range of 60 to 432,000 seconds.
This feature request proposes enabling customers to configure the idle connection tracking timeout during machine pool creation for ROSA clusters. This would ensure that all worker nodes consistently use the desired idle connection timeout value.

3. Why does the customer need this? (List the business requirements here)
By reducing the default idle connection tracking timeout on Nitro v6 instances from 432,000 seconds to 350 seconds, AWS may have introduced compatibility issues for customers with applications that rely on longer-lived idle connections. Customers migrating existing worker nodes from older EC2 instance types to Nitro v6 need the ability to retain higher timeout values to meet application and business requirements.

4. List any affected packages or components.
ROSA worker nodes running on Nitro v6 EC2 instances.

Reference:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/modify-network-interface-attributes.html