Default-enable Multi Cluster Diagnostics

[thomasvn]

What does this PR change?

Default enables the Multi-Cluster Diagnostics primary. The primary is a dedicated goroutine which continually fetches new data from the bucket, aggregates the data, and handles queries.

For users who are leveraging .Values.federatedETL.agentOnly=true for their secondary clusters, we default DIAGNOSTICS_PRIMARY=false to ensure that those secondary agents are not making an unnecessary amount of API requests to the bucket. All other users still have the option to override this new default by setting .Values.diagnostics.primary.enabled=false.

Does this PR rely on any other PRs?

N/A

How does this PR impact users? (This is the kind of thing that goes in release notes!)

Full Multi-cluster diagnostics features are now enabled by default.

Links to Issues or tickets this PR addresses or fixes

N/A

What risks are associated with merging this PR? What is required to fully test this PR?

As mentioned above. If we end up enabling DIAGNOSTICS_PRIMARY=true on all of the user's clusters, we may cause unnecessary overhead in requests to the S3 bucket. The user has the ability to override this change by setting .Values.diagnostics.primary.enabled=false on their secondaries.

How was this PR tested?

TODO

Have you made an update to documentation? If so, please provide the corresponding PR.

TODO

[github-actions]

This pull request has been marked as stale because it has been open for 90 days with no activity. Please remove the stale label or comment or this pull request will be closed in 5 days.