Agreement on how to write connection parameters

[pierluigilenoci]

There is a "small" issue that makes the UpJet AWS provider unusable in conjunction with the SQL provider.
This is because there is a discrepancy between the way the UpJet provider writes credentials and how the SQL provider reads them.
Could the maintainers of both providers discuss and find a solution to unblock all users who would like to create databases and easily execute queries?
List of issues to help you analyze the problem:

• MySQL Instance fills out endpoint field in ConnectionSecret in an unexpected way, breaking crossplane-contrib/sql-provider #778
• Return RDS Instance Endpoint field in the ConnectionSecret without port #798
• Allow writeConnectionSecretToRef to be compatible with SQL community provider #1189
• Agreement on how to write connection parameters #1578
• Remove port from endpoint (if added) provider-sql#154
• Adds port twice when using connectionStrings from upbound/provider-aws-rds provider-sql#191
• Agreement on how to write connection parameters provider-sql#203

[pierluigilenoci]

The follow-up discussion can also be found here: https://crossplane.slack.com/archives/C01718T2476/p1732801643245679.

[Duologic]

For ref, my response on the provider-sql issue: crossplane-contrib/provider-sql#203 (comment)