AwsGlueJobOperator: add run_job_kwargs to Glue job run

[ron-damon]

This PR adds the possibility to set specific Glue job properties for a run instance of an AwsGlueJobOperator without the need to recreate or update the job.
Follows the same approach of the existing create_job_kwargs argument.

This is really useful because you can use the same job with different profiles.

E.g: you can specify a different timeout (Timeout) and size (WorkerType / NumberOfWorkers) for a given table.

# ...
from airflow.providers.amazon.aws.operators.glue import AwsGlueJobOperator
# ...
script_args = {
    "--timestamp": "{{ ts }}",
    "--table": job_table,
}
run_job_kwargs = {
    "Timeout": job_timeout,
    "NumberOfWorkers": job_workers,
    "WorkerType": job_workers_type,
}

upsert_table = AwsGlueJobOperator(
    task_id="upsert_table",
    job_name="upsert-table",
    script_args=script_args,
    run_job_kwargs=run_job_kwargs,
)
# ...

---

^ 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

[kurtqq]

i guess pr is waiting for unit tests?

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions.

[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.

[ferruzzi]

Looks reasonable to me.

[boring-cyborg]

Awesome work, congrats on your first merged pull request!