* implement native sqlite support as a feature flag following [1]
([1] is mentioned as a checklist of sorts as to how to add a new
feature flag in [2])
[1] 13f65f05ae
[2] https://github.com/babashka/babashka/blob/master/doc/build.md
* bump to latest sqlite-jdbc, remove some no longer needed config+libs
based on feedback from borkdude here [1], bump xerial/sqlite-jdbc
3.36.0.3, which includes the graalvm classes and resource config
previously implemented via ericdallo/sqlite-jni-graal-fix and a `-H`
flag in `script/compile`
[1]: https://github.com/babashka/babashka/pull/1079#issuecomment-980533178
* make core.async integral (not a feature)
tasks (in particular, parallel tasks) require core.async
* make rewrite_clj integral (not a feature)
* cleanup mistakes
* put tools.logging behind a feature flag
* add tools.logging.readable
- move logging namespace to feature folder
- add logging.readable namespace
- add tests for logging.readable
* cleanup logging changes
- add logging env var to compile script
- remove unconditional require of logging namespace
* move old-config capture to before alter
* remove feature check from logging tests
- add default test selector to skip "windows only" tests
- in cases where the differences between *nix shell and windows shell
make the test very messy, add a separate "windows only" test
- make more tests work on Windows
* make tests run on windows as the default
- change from selecting tests to run to selecting tests to skip (remove all :windows tags, add
:skip-windows tag to tests that don't currently work on windows)
- handfuls of calls to `normalize` and `escape-file-paths` to handle platform differences
- split `task-test` to make most of the tests run on windows, and exclude just a couple of Unix-y tests
* make a binding name clearer
* skip nrepl-server-test on Windows
- test fails on CI, so disabling it for now
* unset bb environment vars after running tests
* unset bb environment var after running release-artifact
BABASHKA_EDN being set can interfere with some tests, so unset it before running the
native tests
* skip uberjar test on Windows
uberjar-test's 'throw on empty classpath' test failing on Windows native
(but passes on JVM) - skip it for now
