feat: build for release

feat: build for release

🚀 Prepare release (s-weigand#241)

* ⬆️ Bump node version from 12 to 16

* 🚧 Changed @types/node to version 16

* ⬆️ Upgraded jest related dev dependencies to 28

feat: build for release

Bump jest from 26.6.3 to 27.4.5 (s-weigand#182)

* Bump jest from 26.6.3 to 27.4.5

Bumps [jest](https://github.com/facebook/jest) from 26.6.3 to 27.4.5.
- [Release notes](https://github.com/facebook/jest/releases)
- [Changelog](https://github.com/facebook/jest/blob/main/CHANGELOG.md)
- [Commits](jestjs/jest@v26.6.3...v27.4.5)

---
updated-dependencies:
- dependency-name: jest
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

* ⬆️ Upgraded ts-jest

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: s-weigand <s.weigand.phy@gmail.com>

feat: build for release

🩹 Fix env activation (s-weigand#130)

* 🧪 Added workflow job using bash login shell and activate TEST env

* 🧪 Added test for custom env activate with none login shell

* 🩹 Removed env vars from conda activation

Adding the env vars did lead to 'source activate <env_name>' not working anymore see issue 125

* 🧹 Moved parseActivationScriptOutput definition before its first usage

feat: build for release

👌 Use more robust conda activation (s-weigand#124)

* 🧹 Fixed typos in readme

* ♻️ Refactored env activation to use 'conda shell.<shell_name> activate <env_name>'

output instead running a tmp script in a subshell
see s-weigand#12

* 🧪 Added job to check if env activation persists

* 👌 Changed logging to use groups for a cleaner log

* 🧹 Remove env activation test

Env activation will be a feature for v2

* 🧪 Activate env var testing

* 🧹 Removed obsolete warining from readme

* 🧹 Removed insecsure env var logging

feat: Build for release