v2.7.5 breaks backwards compatibility when used against Aurora MySQL

With 2.7.5 and onwards, mariadb driver usage against aurora mysql instances will not work. I realize there are other bugs like this filed against lower versions, but I can confirm the problem does not exist in 2.7.2 and 2.7.4 for instance.

I realize that I can add `?usePipelineAuth=false` and it will workaround the issue but the point is that this is a backwards compatibility breaking change. I am wondering if you have considered reverting the backwards compatibility breaking change for the v2.7.X line. Keeping that change makes it so anyone wanting security fixes will have their workflows broken.

Probably related to CONJ-895

Repro:

1) write an application with a valid aurora mysql instance credentials set for userName and password and provide a "jdbc:mariadb://<aurorahost>:3306/database" for jdbcUrl

try (Connection conn = DriverManager.getConnection(jdbcUrl, userName, password))

2) Provide maria jdbc driver v2.7.5
3) Execute the application

Expected: Successful connection
Actual: Caused by: java.sql.SQLNonTransientConnectionException: Could not connect to address=(host=<MYHOSTNAME>)(port=3306)(type=master) : (conn=34916) could not load system variables

4) Replace the v2.7.5 driver with 2.7.4 and get a successful connection