Move to supported Elastic helm charts

What does this MR do?

Issue: #212564 (closed)

The Elasticsearch chart we use has a deprecation notice. https://github.com/helm/charts/tree/master/stable/elasticsearch#pre-deprecation-notice

From recent PRs on the chart, there is a clear push for us to move to the elastic maintained chart, see for example this comment from a maintainer https://github.com/helm/charts/pull/18620#issuecomment-594544661

This MR moves to a newly created Elastic Stack chart that we maintain and that makes use the official Elastic charts. https://gitlab.com/gitlab-org/charts/elastic-stack

Upgrading to this version is not compatible with the old chart, so as a migration we first uninstall the chart.

I have manually tested upgrades from chart versions 1.9.0 and 2.0.0 and confirmed that everything works in the logging explorer.

Screenshots

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• [-] Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• [-] Tested in all supported browsers
• [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• [-] Label as security and @ mention @gitlab-com/gl-security/appsec
• [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• [-] Security reports checked/validated by a reviewer from the AppSec team