fix(capi-cluster): add labels and annotations to machinepool

[davidspek]

Summary

This PR fixes that the labels and annotations weren't being set on the MachinePool object. This meant that autoscaling wasn't working, since the annotation to specify an external autoscaler is being used needs to be on the MachinePool resource.

Test Plan

Add new unit tests that ensures the labels and annotations from the AWS and GCP node pool defaults and node pool overrides are propagated onto the GCP and AWS managed machine pool and MachinePool resources.

Checklist

• No images hosted from dockerhub
• Are dashboards present to understand the health of the application. There must be at least 1 of these
  • all databases should have dashboards
  • ideally also have at least cpu/mem utilization dashboards for webserver tier of the app
  • you can use plural from-grafana to convert a grafana dashboard found via google to our CRD
• Are scaling runbooks present
  • all databases must have scaling runbooks
  • you can use the charts in pluralsh/module-library to accelerate this
• do you need to add config overlays?
  • inputing secrets
  • configuring autoscaling
• If there’s a web-facing component to the app, we need to support OIDC authentication and setting up private networks if no authentication option is viable
• All major clouds must be supported
  • Azure
  • AWS
  • GCP

[plural-bot]

🎉 This PR is included in version 1.14.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀