[proposal] provide DbtCloudRunJobOperator with an option re-poking the api endpoint if it's a http error

[keerthi-reddiwandla]

We host a dbt jobs DAG in MWAA using DbtCloudRunJobOperator. Sometimes the DbtCloudRunJobOperator get 404 error from the dbt cloud api endpoint even though it has triggered the dbt cloud job run.The task is marked as FAILED and it moves on to next task. It would be helpful to add options after providing following arguments:
1.retry_attempts: if the error is http error, you can provide certain number of retry attempts.
2.retry_after_seconds: Initiate the retry after certain number of seconds.

I can look into opening a PR if you can guide me in a general direction of making this change.

[depowell]

@keerthi-reddiwandla hey Keerthi, i don't think we are meant to use the operator to determine the status of the job, it would probably be better to use the sensor to do that:
https://airflow.apache.org/docs/apache-airflow-providers-dbt-cloud/stable/operators.html#poll-for-status-of-a-dbt-cloud-job-run

[keerthi-reddiwandla]

will look into the DbtCloudJobRunSensor, thank you!