Adds component labels to Operator backed services

[dharmit]

What type of PR is this?
/kind feature

What does this PR do / why we need it:
Adds component labels to Operator backed services. We will need this for:

• odo service list - to list services that belong to a component. Refer odo service create should add operator CR to the devfile #4160 (comment) for more details.
• odo service delete - to delete services from cluster, we will compare the Kubernetes Inlined components in a devfile with the list of services belonging to the component on the cluster

Which issue(s) this PR fixes:

Fixes part of the scope mentioned in #4160 (comment)

PR acceptance criteria:

• Unit test

• Integration test

• Documentation

• I have read the test guidelines

How to test changes / Special notes to the reviewer:
Notes

• There's no integration test on this one because it's not a user facing change. Integration tests will be added in the PR for odo sevice list and odo service delete that use this PR.

How to test

• Create an operator backed service by doing odo service create && odo push. For example - odo service create etcdoperator.v0.9.4-clusterwide/EtcdCluster myetcd && odo push. You could edit the service manifest in devfile.yaml and add labels to it and see if appending the labels works.
• Check for labels - kubectl get EtcdCluster/myetcd -o yaml | less and check for .metadata.labels.

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dharmit

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• pkg/devfile/OWNERS [dharmit]
• pkg/service/OWNERS [dharmit]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[valaparthvi]

1 question, everything else looks good to me.