refine ENI tagging logic

[M00nF1sh]

What type of PR is this?
/kind cleanup
/kind feature

Which issue does this PR fix:
N/A

What does this PR do / Why do we need it:
This PR did following change:

1. All ENIs created by IPAM-D will be tagged with all desired tags on creation.
2. All ENIs managed by IPAM-D will be tagged with all desired tags if not already tagged with these tags. Other tags on ENI will be kept as it is.
   • Trunk ENI is excluded, as it's lifecycle is managed by vpc-resource-controller.
   • Since we tag ENIs on ENI creation, this backfill logic will only trigger for below cases:
     • ENIs created by previous versions of ENI and the desired tag set changed.
     • ENIs attached to instances from external source without the node.k8s.amazonaws.com/no_manage tag.
3. The desired tag set is:
   • node.k8s.amazonaws.com/instance_id: <instance_id>
   • cluster.k8s.amazonaws.com/name: <cluster-name> if CLUSTER_NAME envVar is specified.
   • additional tags specified if ADDITIONAL_ENI_TAGS envVar is specified.

This PR gives us below benefit, which allow customers to use a scoped down IAM policy

• If ENI is configured with CLUSTER_NAME environment variable, ensure ENI is tagged with clusterName tag on creation.
• If ENI is configured with CLUSTER_NAME environment variable, ensure managed ENIs have clusterName tag backfilled.

If an issue # is not available please add repro steps and logs from IPAMD/CNI showing the issue:

Testing done on this change:

Automation added to e2e:

Will this break upgrades or downgrades. Has updating a running cluster been tested?:

Does this change require updates to the CNI daemonset config files to work?:

Does this PR introduce any user-facing change?:

IPAMD now tag ENIs with desired tags on ENI creation and backfill desired tags for ENIs attached to node.

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