Introduce decorator to load providers configuration

[potiuk]

A number of commands in Airflow relies on the fact that
providers configuration is loaded. This is a rather fast operation
as it does not involve any importing of provider classes, just
discovering entrypoints, running them and parsing yaml configuration,
so it is a very low sub-second time to do it.

We cannot do it once in settings/config because we actually need
settings/config to be pre-initialized without providers in order
to be able to bootstrap airflow, therefore we need to run
it individually in each command that can be run with the
"airflow" entrypoint. Decorator seems to be best suited to do
the job:

• easy to apply and not easy to forget when you create another
  command and look at other commands
• nicely wraps around local ProvidersManager import

There are exceptions for the "version" and "providers lazy-loaded"
commands because they are NOT supposed to initialize configuration
of providers.

---

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

Reopened with full tests.

[potiuk]

OK. Should be ready to review now and it has much better/consistent initialization of configuration options contributed by providers. Also enabler for dask/kubernetes provider PRs #32769 #32767 and #32766 - which is a nice optimization of when webserver config is being written.

[hussein-awala]

Looks good! LGTM

[potiuk]

Oh nice. That will let me get all the others smaller :)