Respect @pytest.mark.filterwarnings in prohibited warnings

[Taragolis]

Found this issue when tried to resolve some warnings in tests, in current implementation we add error filter before start the test but when @pytest.mark.filterwarnings already add filter into the warning.filters in this case this code still raise an error

@pytest.mark.filterwarnings("ignore::airflow.exceptions.RemovedInAirflow3Warning")
def test_suite():
    warnings.warn("Surprise Surprise", category=RemovedInAirflow3Warning)

The solution pretty simple add appropriate markers during the tests collection, when test item just collected, and add it before all explicitly set markers. in this case the order of marker execution would be same as this code

@pytest.mark.filterwarnings("ignore::airflow.exceptions.RemovedInAirflow3Warning")
@pytest.mark.filterwarnings("error::airflow.exceptions.RemovedInAirflow3Warning")
@pytest.mark.filterwarnings("error::airflow.utils.context.AirflowContextDeprecationWarning")
@pytest.mark.filterwarnings("error::airflow.exceptions.AirflowProviderDeprecationWarning")
def test_suite():
    warnings.warn("Surprise Surprise", category=RemovedInAirflow3Warning)

which turned into the this order into the warning.filters

00 = {tuple: 5} ('ignore', None, <class 'airflow.exceptions.RemovedInAirflow3Warning'>, None, 0)
01 = {tuple: 5} ('error', None, <class 'airflow.exceptions.RemovedInAirflow3Warning'>, None, 0)
02 = {tuple: 5} ('error', None, <class 'airflow.utils.context.AirflowContextDeprecationWarning'>, None, 0)
03 = {tuple: 5} ('error', None, <class 'airflow.exceptions.AirflowProviderDeprecationWarning'>, None, 0)
...

I've check this behaviour in both pytest 7.4 and pytest 8.1+

---

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

[Taragolis]

An unpleasant side effect: now it also affects warnings in fixtures, e.g. DagBag which collect example DAGs skip all DAGs which contain deprecated stuff, e.g. SubDagOperator. Need to find better way to import it, for now import it with temporary suppress warnings.

[Taragolis]

One more rebase before merge