Configuration file links broken and unversioned

[falko]

The links to the configuration files are currently broken:

camunda-docs/docs/self-managed/zeebe-deployment/configuration/configuration.md

Lines 34 to 37 in a644fe5

	- [`config/application.yaml` Standalone Broker (with embedded gateway)](https://github.com/camunda/zeebe/tree/main/zeebe/dist/src/main/config/application.yaml) - Default configuration containing only the most common configuration settings. Use this as the basis for a single broker deployment for test or development.
	- [`config/broker.standalone.yaml.template` Standalone Broker (with embedded gateway)](https://github.com/camunda/zeebe/tree/main/zeebe/dist/src/main/config/broker.standalone.yaml.template) - Complete configuration template for a standalone broker with embedded gateway. Use this as the basis for a single broker deployment for test or development.
	- [`config/broker.yaml.template` Broker Node (without embedded gateway)](https://github.com/camunda/zeebe/tree/main/zeebe/dist/src/main/config/broker.yaml.template) - Complete configuration template for a broker node without embedded gateway. Use this as the basis for deploying multiple broker nodes as part of a cluster.
	- [`config/gateway.yaml.template`](https://github.com/camunda/zeebe/tree/main/zeebe/dist/src/main/config/gateway.yaml.template) - Complete configuration template for a standalone gateway.

While the Zeebe source code has been moved to a sub-folder the dist folder has not moved, i.e. the files are still here: https://github.com/camunda/zeebe/tree/main/dist/src/main/config

In addition, the files for older versions are available in tags, e.g. https://github.com/camunda/zeebe/tree/8.5.0/dist/src/main/config

So, the versioned docs should link to the corresponding tag or users will have surprises trying to use configuration parameters that don't exist in older versions.

Also the Camunda Docs AI does not know about the contents of these configuration files and can therefore can't answer questions like:

What does ZEEBE_BROKER_EXPORTERS_ELASTICSEARCH_ARGS_INDEX_NUMBER_OF_SHARDS?

[akeller]

@christinaausley can I have you take a look at the link component of this issue in the next two weeks? Having the right versioned links in the docs for each minor makes sense.

Regarding the Camunda Docs AI, we can split this into a separate issue on the Developer Experience repo and explore how we want to handle it. We don't ingest repos, but it might be a point to start that conversation or trial very specific files with config values (and, likely, inline docs).