Clean microsoft azure provider by deleting the custom prefix from conn extra fields

[hussein-awala]

closes: #30557

---

In this PR I fix the UI fields name by removing the custom prefix from Azure conn extra fields, deprecating the used fields with this prefix in order to remove them in the future, clean the documentation, and clean the provider tests.

[eladkal]

We also have entry for Azure in #28790

[hussein-awala]

The method _ensure_prefixes was added in #27041 by @dstandish:

airflow/airflow/providers/microsoft/azure/hooks/fileshare.py

Lines 29 to 33 in 058b6eb

	def _ensure_prefixes(conn_type):
	"""
	Remove when provider min airflow version >= 2.5.0 since this is handled by
	provider manager from that version.
	"""

I don't think we really need to wait until bumping the provider min airflow version to >= 2.5.0, since we check for the two variables (with and without extra_...) in each extra field loading, and with this PR, we will have:

• For the new connections, the extra fields will be created without extra_ prefix -> this should work without any problem
• For the connection which have fields with extra_, when we update them will have a new field without the extra_ prefix and another one with extra_ prefix but with the old value, this old value will not be processed as long as the new one is present in the extra.
• For the connection which have fields with extra_, without any update, the provider will use the fields with the prefix, and a warning will be logged to prompt the user to update the connection extra fields.

WDYT?

[potiuk]

Hmm. I think the problem was that without the "ensure prefixes" providers_manager woudl crash during building the UI fir connections or at least wreak some havoc. I think we would need to build such provder and install it in airflow 2.3 to be sure.

[potiuk]

After defining connection with 2.3 of course.

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions.

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions.

[hussein-awala]

@potiuk I tested this PR with 2.4.0 (the current min version) and with main, I can create connections with and without the extra__azure__ prefix without any issue. What kind of tests should I do before merging it?
And for this commet:

Hmm. I think the problem was that without the "ensure prefixes" providers_manager woudl crash during building the UI fir connections or at least wreak some havoc. I think we would need to build such provder and install it in airflow 2.3 to be sure.

There is no problems with the UI:



(6.2.3 because I built it with breeze and installed it from source in a clean conda env)

[potiuk]

I can't remember exactly (the comment was from more than 3 months ago) but I believe it was based on "providers back-compat tests" failing back then. We moved to 2.4 min version since, so I think this is good to go now - maybe because of back-compat problem going away because of the min-airflow version bump :)