[EKS] [feature request]: Tags for ELB ALB Rules

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**
Add tags to rules in load balancers listeners, so each rule can have its own tags. Use-case is to have multiple source of truth for rules - for example some rules could be created by AWS Ingress Controller, some manually - and they won't interfere with each other.

**Which service(s) is this request for?**
EKS, EC2 Load Balancer

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
We have some redirect rules, which we don't want to describe in Ingress Definition, because they are a lot and some of them are not related to the project at all. Its impossible to have this now, as AWS Ingress Controller deletes all rules not managed by it. Adding tags will allow to have rules from different sources and they wont interfere with each other, just like External DNS controller adds tags(in form of txt record) to the DNS records, and it will not touch records not owned by it.

Rule1: (managed-by: aws-controller)
Rule2: (managed-by: null)
Rule3: (managed-by: terraform)

in this example, aws-controller won't delete rule 2 and 3, because they are not managed-by it.

**Are you currently working around this issue?**
We added another load balancer, which contains only rules for redirect.

**Additional context**
N/A

**Attachments**
N/A

Review the EKS and EC2 Load Balancer context described in the request, including how AWS Ingress Controller-managed rules coexist with manually or Terraform-managed rules. Done means rules can carry ownership tags and the controller preserves rules owned by other sources, but the issue names no repository files or tests to start from.

Written by the indexing model from the issue text.