feat(mcp-connector): add mcp-connector as composition

[haarchri]

Description of your changes

• add mcp-connector as composition

Fixes #

I have:

• Read and followed Upbound's contribution process.
• Run make reviewable to ensure this PR is ready for review.
• Added backport release-x.y labels to auto-backport this PR, as appropriate.

How has this code been tested

KUBECONFIG=init/mcp.yaml kubectl get secrets aws-spoke-01-kubeconfig  -n default -o jsonpath="{.data.kubeconfig}" | base64 -d >>  init/kubeconfig-aws-spoke-01.yaml

KUBECONFIG=init/kubeconfig-aws-spoke-01.yaml kubectl api-resources | grep "upbound"
clusters                                       aws.caas.upbound.io/v1alpha1             true         Cluster
connectors                                     mcp.caas.upbound.io/v1alpha1             true         Connector

KUBECONFIG=init/kubeconfig-aws-spoke-01.yaml kubectl get pods -A | grep "mcp"
kube-system   mcp-connector-7bd57b9b49-4svnk             2/2     Running   0          23m

[ytsarev]

Left some comments.

It's already quite complex logic here, should we start to introduce uptest into the flow?

[haarchri]

@ytsarev i will create a PR to introduce uptest for configuration-caas repo

[ytsarev]

LGTM