Prepare release for Sep 2025 1st wave of providers

[eladkal]

Summary of prepared documentation:

Success: 32

amazon apache.beam apache.kafka celery cncf.kubernetes common.messaging common.sql databricks dbt.cloud edge3 fab git google http jdbc keycloak microsoft.azure mysql neo4j openlineage oracle pinecone postgres redis salesforce samba sftp
slack smtp snowflake standard weaviate

Docs only: 61

airbyte alibaba apache.cassandra apache.drill apache.druid apache.flink apache.hdfs apache.hive apache.iceberg apache.impala apache.kylin apache.livy apache.pig apache.pinot apache.spark apache.tinkerpop apprise arangodb asana
atlassian.jira cloudant cohere common.compat datadog dingding discord docker elasticsearch exasol facebook ftp github grpc hashicorp imap influxdb jenkins microsoft.mssql microsoft.psrp microsoft.winrm mongo odbc openai openfaas opensearch
opsgenie pagerduty papermill pgvector presto qdrant segment sendgrid singularity sqlite tableau teradata trino vertica ydb zendesk

Skipped on no changes: 4

common.io yandex ssh telegram

[jscheffl]

@eladkal as I am in #53563 and a few follow-ups adding the new React UI for edge3 to be ready for Airflow 3.1 it might be that we have an intermediate state and a set of small changes defeat the stability of provider docs in changelog. It might be easier to skip edge3 release (no critical fix needing a release atm) and rather consider making an ad-hoc with Airflow 3.1 release time?

[eladkal]

@eladkal as I am in #53563 and a few follow-ups adding the new React UI for edge3 to be ready for Airflow 3.1 it might be that we have an intermediate state and a set of small changes defeat the stability of provider docs in changelog. It might be easier to skip edge3 release (no critical fix needing a release atm) and rather consider making an ad-hoc with Airflow 3.1 release time?

I updated the release to include the latest PR merged
if we will have bug fixes later we can consider ad-hoc release. It could be that these bug fixes would be synced with next wave anyway.