fix: Make using Java's ServiceLoader optional on Database.connect()

[makeevrserg]

Description

Summary of the change: Make using ServiceLoader for DatabaseConnectionAutoRegistrationnot optional

Detailed description:

• What: connectionInstanceImpl doesn't need to be created using java ServiceLoader.
• Why: In some cases with different loaders it may throw exception even if existing interface implementation is present. Also this may improve stability as reflection will not be required during connection.
• How: The connectionInstanceImpl is now lazy-loaded so even if ServiceLoader doesn't have required service, code block will not crash. Every connect method have now connectionAutoRegistration as a parameter instead of previous private-service-loaded
• This also relevant to older issues on github, which is marked as closed, but still could be reproduced located below
• This also may be a small step in migration to KMP if it's planned.

---

Type of Change

Please mark the relevant options with an "X":

• Bug fix
• New feature
• Documentation update

Updates/remove existing public API methods:

• Is breaking change

Affected databases:

• MariaDB
• Mysql5
• Mysql8
• Oracle
• Postgres
• SqlServer
• H2
• SQLite

Checklist

• Unit tests are in place
• The build is green (including the Detekt check)
• All public methods affected by my PR has up to date API docs
• Documentation for my change is up to date

---

Related Issues

• Issue with relocation using Shadow Jar #1353
• Can't load implementation for DatabaseConnectionAutoRegistration #971
• Can't load implementation for DatabaseConnectionAutoRegistration #792
• Can't load implementation for DatabaseConnectionAutoRegistration #748

[bog-walk]

Thanks for working on this PR @makeevrserg !
Please consider rebasing from main and addressing the suggested changes.

[e5l]

thanks for the contribution, lgtm!