external-dns-private in cluster-azure should include depends-on annotation

[AverageMarcus]

Bug description

Currently cluster creation of private CAPZ WCs can get stalled for quite a long while due to the following error:

{"level":"info","ts":"2024-10-11T10:54:01Z","msg":"App status for 't-gbgz43j01klo9wxi2k-external-dns-private' is not yet as expected: expectedStatus='deployed' actualStatus='invalid-manifest' (reason: 'invalid manifest error: (unable to build kubernetes objects from release manifest: resource mapping not found for name: \"external-dns-private\" namespace: \"kube-system\" from \"\": no matches for kind \"ServiceMonitor\" in version \"[monitoring.coreos.com/v1\](http://monitoring.coreos.com/v1/)"\nensure CRDs are installed first)')"}

Even though the CRDs get installed it takes a considerable amount of time before the external-dns-private App is re-reconciled and installed successfully. This can lead to it taking aprox 10 minutes for all Apps to be installed.

Designed behavior

As external-dns-private (see here) makes use of ServiceMonitor it should specify app-operator.giantswarm.io/depends-on: prometheus-operator-crd.

Reproduction Steps

Easiest way to reproduce it to launch the capz/private WC E2E test suite from cluster-test-suites

Technical information

The external-dns currently does have the annotation so it makes sense to add it to the private one also.