feat(pluto) Database initialisation and connection state checking

[elribonazo]

Overview

This fixed Pluto from not being capable of detecting if the database connection already exists or not. If we left it like this we could not prevent the user from running a query on a non established connection.

First, have improved the DBConnection expects and implemented each variation that we required.
Integrated all the required files for Javascript (browser,nodejs) support with sqljs wasm.
Integrated minimal test coverage running an all platforms.
Added Database start and stop commands to establish or close a connection.
Improved error handling a lot, on Android when application context is not send, and in the rest of pluto when something is queries without an active connection.
Also added an extension for the SQLDriver in order to be capable of telling if the connection is active or closed.

My PR contains...

• No code changes (changes to documentation, CI, metadata, etc.)
• Bug fixes (non-breaking change which fixes an issue)
• Improvements (misc. changes to existing features)
• Features (non-breaking change which adds functionality)

[hamada147]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ JAVASCRIPT	standard	4	4	0	2.72s
✅ KOTLIN	ktlint	24	2	0	49.76s
✅ REPOSITORY	checkov	yes		no	11.7s
✅ REPOSITORY	devskim	yes		no	0.73s
✅ REPOSITORY	dustilock	yes		no	0.02s
✅ REPOSITORY	git_diff	yes		no	0.01s
✅ REPOSITORY	secretlint	yes		no	1.21s
✅ REPOSITORY	syft	yes		no	0.88s
✅ REPOSITORY	trivy	yes		no	2.98s

See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

MegaLinter is graciously provided by