Make sqlalchemy optional dependency for openlineage provider

[sunank200]

Makes SQLAlchemy an optional dependency for the OpenLineage provider by adding it as an optional extra.

• Wrapped sqlalchemy imports with try/except and raise AirflowOptionalProviderFeatureException when missing
• Users who need SQL lineage features should install: pip install 'apache-airflow-providers-openlineage[sqlalchemy]'

closes: #59904

---

^ 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 airflow-core/newsfragments.

[potiuk]

Nice - few questions - but more to openlineage Airflow 3 integration :)

[kacpermuda]

One more note, in utils.py we're also using some db methods like DagRun.fetch_task_instances here, but we only call it on scheduler. We're also going to add another call to db here for asset triggered dagruns, also performed only on scheduler. Not sure how this relates to treating sqlalchemy as optional.

[potiuk]

One more note, in utils.py we're also using some db methods like DagRun.fetch_task_instances here, but we only call it on scheduler. We're also going to add another call to db here for asset triggered dagruns, also performed only on scheduler. Not sure how this relates to treating sqlalchemy as optional.

Not yet. This will come later when we will split (some) providers into two types of providers (maybe they won't be named like that) - we've been disussing it but deferred decision on that to after we complete task isolation and separated core and task-sdk. We iwll have to separate some distributions in two:

• executors/ui plugins/scheduler listeners and plugins (installable with airflow-core)
• Hooks/Operators/macro plugins etc. (installable with task-sdk)

This falls in the same part - part of the current openlineage provider should be a distribution installed with "task-sdk" and part should be another distribution installed with "airflow-core".

Later we can even split "airflow-ui" as separate distribution and have 3 types of "providers"

[potiuk]

Nice!