adding dataproc cluster start and stop operators

[arezamoosavi]

---

^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contribution Guide (https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst)
Here are some useful points:

• Pay attention to the quality of your code (flake8, mypy and type annotations). Our pre-commits will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it’s a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[lwyszomi]

Generally look good but could you fix styling in your code.

[lwyszomi]

same for this operator.

[arezamoosavi]

the same here.

[arezamoosavi]

I rebased the updates on dataproc and create this PR

[lwyszomi]

same here

[arezamoosavi]

it has been fixed in another PR so I rebased the updates on dataproc and create this PR

[josh-fell]

You could simply the implementation in the operator by having hook as an instance attribute of the operator. Using the instance attribute, you wouldn't have to pass the object around and the other methods like _get_cluster() and _start_cluster() could be replaced by simply calling self.hook.get_cluster() and self.hook.start_cluster() directly.

[arezamoosavi]

done, I rebased the updates on dataproc and create this PR

[josh-fell]

Same comment here re: using an instance attribute for the hook object.

[josh-fell]

This (and other) formatting changes look unrelated, and the static checks in the CI probably won't like them. You could run these static checks locally though. Check out this guide for some pointers.

[arezamoosavi]

done, thanks for the feedback.

[potiuk]

You need to rebase :)