Move version imports to inside utils standard provider

[gopidesupavan]

Version imports causing issues when using from init : #44011
#44011 (comment)

---

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

[eladkal]

cc @potiuk

[potiuk]

This is strange error

[gopidesupavan]

Not sure one test is failing..
https://github.com/apache/airflow/actions/runs/11835585982/job/32982431658?pr=44018#step:12:1349

[potiuk]

Applying full tests needed should help

[potiuk]

The problem is that "sdist" test build new providers and try to install them, and they do it in "chunks" - and only for providers affected in this PR. This is a bit missing piece - this PR only modifies the standard provider but no common.sql 1.20 that it depends on, so it misses 1.20 version locally built.

We could likely solve it by smarter selection which providers should be built for sdist builds, but for now "full tests needed" should be enough - also this will go away after we merge this one an release common.sql 1.20 , and applying "full tests needed" should solve the problem as all provider's sdist will be built.

[eladkal]

We could likely solve it by smarter selection which providers should be built for sdist builds, but for now "full tests needed" should be enough - also this will go away after we merge this one an release common.sql 1.20 , and applying "full tests needed" should solve the problem as all provider's sdist will be built.

Yeah the problem should not happen after merging to main.
We can open a followup task in Github issue to get it done when we have the time

[potiuk]

We can open a followup task in Github issue to get it done when we have the time

Yeah. I was adding it as you wrote it :) #44023

[gopidesupavan]

The problem is that "sdist" test build new providers and try to install them, and they do it in "chunks" - and only for providers affected in this PR. This is a bit missing piece - this PR only modifies the standard provider but no common.sql 1.20 that it depends on, so it misses 1.20 version locally built.

We could likely solve it by smarter selection which providers should be built for sdist builds, but for now "full tests needed" should be enough - also this will go away after we merge this one an release common.sql 1.20 , and applying "full tests needed" should solve the problem as all provider's sdist will be built.

oh i see, good learning bit to know this :)

[gopidesupavan]

tests are failing for openlineage, created this #44025