#16691 Providing more information in docs for DataprocCreateCluster operator migration

[pateash]

closes: #16911

Add meaningful description above

I am proposing to add a bit more information in the documentation regarding usage of DataprocClusterCreateOperator() as per refactoring in #6371, users find it a bit difficult to generate CLUSTER_CONFIG.

[pateash]

[github-actions]

The PR is likely OK to be merged with just subset of tests for default Python and Database versions without running the full matrix of tests, because it does not modify the core of Airflow. If the committers decide that the full tests matrix is needed, they will add the label 'full tests needed'. Then you should rebase to the latest main or amend the last commit of the PR, and push it with --force-with-lease.

[guptaneha0908]

@pateash I am facing similar issue with DataprocCreateClusterOperator as well(Airflow 2+) . Also I see metadata field in DataprocCreateClusterOperator is of type Sequence[Tuple[str, str]] but the ClusterGenerator() has type dict for metadata field.
This seems to contradict. I see this branch is merged. Also as per my knowledge ClusterGenerator() is deprecated method. Could you let me know the fix for newer Operator

[pateash]

@pateash I am facing similar issue with DataprocCreateClusterOperator as well(Airflow 2+) . Also I see metadata field in DataprocCreateClusterOperator is of type Sequence[Tuple[str, str]] but the ClusterGenerator() has type dict for metadata field. This seems to contradict. I see this branch is merged. Also as per my knowledge ClusterGenerator() is deprecated method. Could you let me know the fix for newer Operator

@guptaneha0908 ClusterGenerator() has been kept for easy migration, ideally you should have our CLUSTER_CONFIG as dictionary. You can avoid using ClusterGenerator by creating CLUSTER_CONFIG from it once and then storing that dictionary and passing to DataProcClusterCreateOperator going forward.