1. Proposed title of this feature request

Apply user defined tags to all resources created by Openshift in AWS.

2. What is the nature and description of the request?
When preparing the installation of an OCP 4 cluster it is possible to define a list of tags in the install-config.yaml file:
…
platform:
   aws:
     region: us-west-2
     userTags:
         adminContact: jdoe
         costCenter: 7536
...
These tags are applied to the resources created by the IPI intaller (terraform) and also added to the machineset definitions for the workers. However other resources created by Openshift don't get these user defined tag, like:

Classic load balancers, associated with the default ingress controller or any other ingress controller of type Load Balancing created later.
S3 bucket for internal image registry storage
EBS volumes created from a storage class, (PV/PVC)
IAM users: Image registry;Ingress; Machine API

The request is that any resource created for the cluster in AWS, by the installer (IPI) or after installation (IPI or UPI), that gets the tag kubernetes.io/cluster/<cluster id>, also gets the tags defined in the istall-config.yaml file. A plus would be to have these tags in a configmap so that they can be updated after installation.

3. Why does the customer need this? (List the business requirements here)
The customer makes a heavy use of tags to organize many aspects of internal operations in relation with the resources created in AWS, like backups, project allocation and cost calculation, team assignment, etc. Having to tag the resources manually is an inconvenience and prone to error, specially when Openshift is doing it partially with via the installer and later with the kubernetes.io/cluster/<cluster id> tag.