Support passing annotations and labels to build pods from a BuildConfig

1. Proposed title of this feature request

Passing Annotations and Labels to Builds Pods from a BuildConfig

2. What is the nature and description of the request?

Customers would like to be able to to pass annotations to a build pod to take advantage of features such as attaching a pod to an additional network.

https://docs.openshift.com/container-platform/4.10/networking/multiple_networks/attaching-pod.html

Similarly, passing labels for CNI plugin that supports Egress https://cloud.redhat.com/blog/guide-to-kubernetes-egress-network-policies - there is no way to add labels to a build pods to target a network policy to them to allow egress to websites like github.

3. Why does the customer need this? (List the business requirements here)

Customer has private and restricted repositories that are needed at build time. These repos are not accessible via the default network and they want to be able to add a secondary network to preform their builds within OpenShift. Additionally, egress is be restricted and polices need to be applied to build pods to allow access.

4. List any affected packages or components.

BuildConfigs