Fix import future annotations in venv jinja template

[phi-friday]

---

The following Task, when rendered as a jinja template, will result in an error because Any is not imported

from __future__ import annotations
from typing import Any

@task.docker(image='some_image')
def some_task(value: dict[str, Any]) -> Any:
    ...

Changing it to a string like this will solve this problem, but it's a bit cumbersome.

from __future__ import annotations
from typing import Any

@task.docker(image='some_image')
def some_task(value: "dict[str, Any]") -> "Any":
    ...

It would be much easier if I could check if annotations is imported when rendering with jinja.

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

The test will have to be skipped on airflow pre 2.10 because it will not work there (See failing compatibility tests) and ways how to deal with the compatibility issues: https://github.com/apache/airflow/blob/main/contributing-docs/testing/unit_tests.rst#implementing-compatibility-for-provider-tests-for-older-airflow-versions

[phi-friday]

First, I changed the test to only work with airflow>=2.10.
But looking at the output, I don't think it's a change to airflow[docker].

Should I change the test location and remove the airflow 2.10+ condition?

[phi-friday]

Changed the location, as it affects venv operator.

[phi-friday]

It passes all the tests, but maybe there's a problem with the wrong label.
@potiuk Could you change it and run action again?

[potiuk]

It passes all the tests, but maybe there's a problem with the wrong label. @potiuk Could you change it and run action again?

Ah yeah - now it's not a "docker provider" test - it runs only in 'airflow core` and that's correct, because it affects all the decorators not only docker, and it should not be "provider" test as it was before.