[DOCS] The docs section about "dependencies" is outdated

[jonathanlukas]

Describe the issue:

The docs section describing the dependencies structure is outdated. The current helm chart is not an umbrella chart anymore, in fact all camunda components have been internalised.

[aabouzaid]

@jonathanlukas Could you please add the link to the part you mean?

[jonathanlukas]

@aabouzaid this one:

8.6

camunda-platform-helm/charts/camunda-platform-8.6/README.md

Lines 61 to 103 in 2b8078e

	## Dependencies
	Camunda 8 Helm chart is an umbrella chart for different components. Some are internal (sub-charts),
	and some are external (third-party). The dependency management is fully automated and managed by Helm itself;
	however, it's good to understand the dependency structure. This third-party dependency is reflected in the Helm chart
	as follows:
	```text
	camunda-platform
	|_ elasticsearch
	|_ identity
	|_ keycloak
	|_ postgresql
	|_ optimize
	|_ operate
	|_ tasklist
	|_ zeebe
	|_ postgresql
	```
	> [!NOTE]
	> Please note that the Connectors and Web Modeler components are part of the main chart and not implemented as sub-charts.
	For example, Camunda Identity utilizes Keycloak and allows you to manage users, roles, and permissions
	for Camunda 8 components.
	- Keycloak is a dependency for Camunda Identity, and PostgreSQL is a dependency for Keycloak.
	- Elasticsearch is a dependency for the Camunda chart, which is used in Zeebe, Operate, Tasklist, and Optimize.
	- PostgreSQL is an optional dependency for the Camunda chart and is used by Web Modeler.
	The values for the dependencies Keycloak and PostgreSQL can be set in the same hierarchy:
	```yaml
	identity:
	[identity values]
	keycloak:
	[keycloak values]
	postgresql:
	[postgresql values]
	postgresql:
	[postgresql values]
	```

8.7

camunda-platform-helm/charts/camunda-platform-8.7/README.md

Lines 61 to 103 in 2b8078e

	## Dependencies
	Camunda 8 Helm chart is an umbrella chart for different components. Some are internal (sub-charts),
	and some are external (third-party). The dependency management is fully automated and managed by Helm itself;
	however, it's good to understand the dependency structure. This third-party dependency is reflected in the Helm chart
	as follows:
	```text
	camunda-platform
	|_ elasticsearch
	|_ identity
	|_ keycloak
	|_ postgresql
	|_ optimize
	|_ operate
	|_ tasklist
	|_ zeebe
	|_ postgresql
	```
	> [!NOTE]
	> Please note that the Connectors and Web Modeler components are part of the main chart and not implemented as sub-charts.
	For example, Camunda Identity utilizes Keycloak and allows you to manage users, roles, and permissions
	for Camunda 8 components.
	- Keycloak is a dependency for Camunda Identity, and PostgreSQL is a dependency for Keycloak.
	- Elasticsearch is a dependency for the Camunda chart, which is used in Zeebe, Operate, Tasklist, and Optimize.
	- PostgreSQL is an optional dependency for the Camunda chart and is used by Web Modeler.
	The values for the dependencies Keycloak and PostgreSQL can be set in the same hierarchy:
	```yaml
	identity:
	[identity values]
	keycloak:
	[keycloak values]
	postgresql:
	[postgresql values]
	postgresql:
	[postgresql values]
	```

This section is present in all versions up to now, but the actual structure changed some time ago.