feat: Improve enforcement of SSL for dbConnect() and the output when printing connections

[d-hansen]

• Removed unnecessary casting in mysql_options (do not need to explicitly cast to void *)
• Remove long since deprecated and removed flag CLIENT_SECURE_CONNECTION
• Added CLIENT_SSL_VERIFY_SERVER_CERT
• Added some documentation about using SSL with the client.flag including CLIENT_SSL.
• Cleaned up and added information to show output for a DB Connection. Output now looks something like:

<MySQLConnection>
  Hostname:       my-database-1.xyzzy.us-east-1.rds.amazonaws.com
  Username:       r_user
  Database:       r_test_db
  Server Port:    3306
  Connection:     my-database-1.xyzzy.us-east-1.rds.amazonaws.com via TCP/IP
  Protocol:       10
  SSL Cipher:     ECDHE-RSA-AES128-GCM-SHA256
  Thread Id:      10615
  Client Version: 5.7.44
  Client Flags:   01BEAA8D
  Server Version: 8.0.35
  Capabilities:   DFFFFFFF
  SQL Status:     00000000

[aviator-app]

Current Aviator status

Aviator will automatically update this comment as the status of the PR changes.
Comment /aviator refresh to force Aviator to re-examine your PR (or learn about other /aviator commands).

This PR was merged manually (without Aviator). Merging manually can negatively impact the performance of the queue. Consider using Aviator next time.

---

See the real-time status of this PR on the Aviator webapp.

Use the Aviator Chrome Extension to see the status of your PR within GitHub.

[krlmlr]

Thanks!

[d-hansen]

Not sure what was the problem with the macos build trying to get R... Probably the R feed was getting updated and temporarily unavailable.

[krlmlr]

Thanks!

[aviator-app]

This pull request failed to merge: PR cannot be automatically rebased, please rebase manually to continue. Once the issues are resolved, remove the blocked label and re-queue the pull request. Note that the pull request will be automatically re-queued if it has the mergequeue label.

Additional debug info: Failed to rebase this PR onto the latest changes from the base branch. You will probably need to rebase this PR manually and resolve conflicts).