Fix side effects in DBT Cloud tests

[Taragolis]

Fixup flakey test tests/providers/dbt/cloud/operators/test_dbt.py::TestDbtCloudRunJobOperator::test_execute_wait_for_termination which depends on a system time. As a bonus test run time is reduced

            else:
                # When the job run status is not in a terminal status or "Success", the operator will
                # continue to call ``get_job_run()`` until a ``timeout`` number of seconds has passed
                # (3 seconds for this test).  Therefore, there should be 4 calls of this function: one
                # initially and 3 for each check done at a 1 second interval.
>               assert mock_get_job_run.call_count == 4
E               AssertionError: assert 3 == 4
E                +  where 3 = <MagicMock name='get_job_run' id='140043051658976'>.call_count

tests/providers/dbt/cloud/operators/test_dbt.py:264: AssertionError

In addition changed current directory in tests where we provide relative paths, otherwise this is a matter of time when we accidentally merge in main branch files test-generated

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an 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 a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

[potiuk]

NICE!

[josh-fell]

🔥