Connector dependency action report improvements

[pedroslopez]

We have this action which reports the affected connectors a given PR is touching. It's useful to know whether your changes unexpectedly affect other parts of the codebase, however, it's often spammy and not easy to parse when there are many connectors affected.

We should:

• Stop commenting on every commit. Instead, we can either comment once and update the same comment or make a new comment if the content has changed.
• Rather than having a single list of affected connectors, we could split it up with collapsible segments for sources and destinations.

---

Example:

NOTE ⚠️ Changes in this PR affect the following connectors. Make sure to run corresponding integration tests:

Sources (3)

• source-cockroachdb
• source-clickhouse
• source-snowflake

Destinations (5)

• source-oracle
• destination-clickhouse-strict-encrypt
• destination-local-json
• destination-mssql-strict-encrypt
• destination-mssql

[evantahler]

Let's use this issue instead of #18019

[erohmensing]

closed in #18480