fix: elasticsearch in HC is disabled by default

[jessesimpson36]

Description

One of the decisions made as part of the Liquibase epic and the RDBMS epic is that we no longer want people to view Elasticsearch as the preferred method of installing the helm chart. We want to present it as one of 3 valid options. In support of that idea, this PR goes through all of the code snippets related to using elasticsearch, and inserts the options global.elasticsearch.enabled=true and elasticsearch.enabled=true so that those snippets will be functional after this change.

I also included an announcement explaining the change.

Task disabling elasticsearch in HC by default:
camunda/camunda-platform-helm#4671

Liquibase epic: https://github.com/camunda/product-hub/issues/3023

RDBMS epic: https://github.com/camunda/product-hub/issues/2690

Alternative infrastructure services: https://github.com/camunda/product-hub/issues/3098
(relevant from this line)

From Camunda 8.9, sub-charts for PostgreSQL, Elasticsearch, and Keycloak will be disabled by default.

And related to this: #7317

When should this change go live?

• This is a bug fix, security concern, or something that needs urgent release support. (add bug or support label)
• This is already available but undocumented and should be released within a week. (add available & undocumented label)
• This is on a specific schedule and the assignee will coordinate a release with the Documentation team. (create draft PR and/or add hold label)
• This is part of a scheduled alpha or minor. (add alpha or minor label)
• There is no urgency with this change (add low prio label)

PR Checklist

• The commit history of this PR is cleaned up, using {type}(scope): {description} commit message(s)

• My changes are for an upcoming minor release and are in the /docs directory (version 8.9).
• My changes are for an already released minor and are in a /versioned_docs directory.

• I added a DRI, team, or delegate as a reviewer for technical accuracy and grammar/style:
  • Engineering team review
  • Technical writer review via @camunda/tech-writers unless working with an embedded writer.

[github-actions]

👋 🤖 🤔 Hello, @mesellings! Did you make your changes in all the right places?

These files were changed only in docs/. You might want to duplicate these changes in versioned_docs/version-8.8/.

• docs/reference/announcements-release-notes/890/890-announcements.md
• docs/self-managed/deployment/helm/cloud-providers/amazon/amazon-eks/irsa.md
• docs/self-managed/deployment/helm/configure/authentication-and-authorization/microsoft-entra.md
• docs/self-managed/deployment/helm/configure/database/elasticsearch/using-external-elasticsearch.md
• docs/self-managed/deployment/helm/configure/database/using-external-opensearch.md
• docs/self-managed/deployment/helm/configure/enable-additional-components.md
• docs/self-managed/deployment/helm/install/quick-install.md
• docs/self-managed/deployment/helm/upgrade/helm-880-890.md

You may have done this intentionally, but we wanted to point it out in case you didn't. You can read more about the versioning within our docs in our documentation guidelines.

[mesellings]

Lgtm @jessesimpson36 I made a few edits around rewording and moving it to the top as a breaking change - does this need to be held back until alpha-2 has been released, or can it go out now?

[jessesimpson36]

@mesellings I don't think we need to wait for after alpha2 for this docs update as it only affects 8.9, but we are only planning on merging the helm-chart change after alpha2 is already released. Worst case scenario, someone gets a little confused testing an alpha and asks us in ask-self-managed and I answer. No harm in merging / deploying this early.

[mesellings]

@mesellings I don't think we need to wait for after alpha2 for this docs update as it only affects 8.9, but we are only planning on merging the helm-chart change after alpha2 is already released. Worst case scenario, someone gets a little confused testing an alpha and asks us in ask-self-managed and I answer. No harm in merging / deploying this early.

Thanks @jessesimpson36 we might as well hold it back now for a few days, then push it 👍