Fix 3.12 failing providers tests of amazon emr hook

[insomnes]

During provider migration deprecation warning ignore was wrongly changed due to misconfigured pre-commit hooks.
now there are cases of failing tests on 3.12:

• https://github.com/apache/airflow/actions/runs/13228919085/job/36923609083
• https://github.com/apache/airflow/actions/runs/13226178126/job/36917628314

Now that pre-commit hooks are fixed in #46603 the problem with failing pipelines can be addressed too:
We need to ignore the actual DeprecationWarning and not AirflowProviderDeprecationWarning cause it's not the provider deprecation mark but in botocore lib.

---

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

[insomnes]

If I understood it correctly changes from here are required first:

#46608

To address other providers deprecation problems in full-tests

[potiuk]

Would love to get it merged to fix the main failures. But it needs to get green :)

[insomnes]

I cannot understand the exact reason for the failure of the check, my initial thought was about deprecations_ignore.yml but it seems unrelated to the AriflowProviderDeprecationsWarning in google tests.

[insomnes]

I can only say that the problems look the same as they were for

• Remove Airflow 3 Deprecation Warning dependency in OTel Provider #46600
• Remove Airflow 3 Deprecation Warning in Google Provider, Move to Private Warning #46599

[insomnes]

After investigation, I am sure that the problem with google deprecation warning failures is outside of this PR scope, should be fine after #46638 or another PR that would fix the problem