Expose information Airflow <-> Providers to users

Currently our users have no insight of which providers are linked ("constraints") to specific Airflow version. We have that information in constraints, but this is not easily browseable. However many times users want to know about a single provider - how it changed between two different versions.

This is not strictly security related, but this could be part of the version inforamation publishing that we do for SBOMS and the same sources (generated/providers_metadata.json) could be used.

Start by inspecting generated/providers_metadata.json and the existing version-information publishing work that also feeds SBOMs. Determine how to expose the Airflow-to-provider constraints for browsing and comparison between Airflow versions; done means users can identify linked providers for a specific version and see how one provider changed across versions.

Written by the indexing model from the issue text.