Prepare release for June 2025 provider wave

[eladkal]

Summary of prepared documentation:

Success:  31

airbyte alibaba amazon apache.hdfs celery cncf.kubernetes cohere common.compat common.sql databricks edge3 fab google hashicorp microsoft.azure mongo mysql neo4j openlineage oracle pinecone sendgrid
sftp slack snowflake standard trino weaviate http influxdb git

Docs only:  4

apache.tinkerpop arangodb docker odbc

Skipped on no changes: 61

apache.beam apache.cassandra apache.drill apache.druid apache.flink apache.hive apache.iceberg apache.impala apache.kafka apache.kylin apache.livy apache.pig apache.pinot apache.spark apprise asana
atlassian.jira cloudant common.io common.messaging datadog dbt.cloud dingding discord elasticsearch exasol facebook ftp github grpc imap jdbc jenkins microsoft.mssql microsoft.psrp
microsoft.winrm openai openfaas opensearch opsgenie pagerduty papermill pgvector postgres presto qdrant redis salesforce samba segment singularity smtp sqlite ssh tableau telegram teradata vertica
yandex ydb zendesk

[jscheffl]

Looks good!

One PR just merged for edge3 and one is in review. Would they be able to slip-in or have you cut the provider wave already?

[eladkal]

One PR just merged for edge3 and one is in review. Would they be able to slip-in or have you cut the provider wave already?

I added all merged PRs. Do we need to wait for specific PR?

[jscheffl]

One PR just merged for edge3 and one is in review. Would they be able to slip-in or have you cut the provider wave already?

I added all merged PRs. Do we need to wait for specific PR?

I'd wish for #51733 and also #51716 will be merged after a final check in ~10min or so... if not too late.

[eladkal]

One PR just merged for edge3 and one is in review. Would they be able to slip-in or have you cut the provider wave already?

I added all merged PRs. Do we need to wait for specific PR?

I'd wish for #51733 and also #51716 will be merged after a final check in ~10min or so... if not too late.

We have time