A simple guide based on the example_dataproc file. Addressing this issue

notes/qs

• @mik-laj All the examples we have of job configurations are added in the guide. Maybe it is too much, but I assumed people will probably just search through the page.
• Is an explanation of the arguments needed? The operators themself are richly documented already so I kept it out for now.

Make sure to mark the boxes below before creating PR: [x]

• Description above provides context of the change
• Unit tests coverage for changes (not needed for documentation changes)
• Target Github ISSUE in description if exists
• Commits follow "How to write a good git commit message"
• Relevant documentation is updated including usage instructions.
• I will engage committers as explained in Contribution Workflow Example.

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.
Read the Pull Request Guidelines for more information.