To provide this ability within Core following has been added:
- Configure fallback show and id in Engine config
- Ability to configure certain Engine Core option from within Engine
- Extend annotated metadata in queues
- Consolidate Resource IDs
- Initial func call for metadata update for analog-in & stream channels

With the newest version of jinja2 flask
stopped working in the 1.1.2 version.
Updating flask to 2.0.3 fixes this issue
and doesn't seem to cause further errors.

Fixes #106

- To be able to configure the compoment without having to add the engine.ini to the meta repository,
	the docker image now expects configurable variable to be passed as environment variables

Config ctrl channel

See merge request !14

- Add release stage to existing Gitlab pipeline
- Add docker build and push job
- Add create release job
- Add neccessary release-notes folder

Now the minimum required python version is mentioned in just two places:
* `.gitlab-ci.yml`
* `docs/bare-metal-installation.md`

chore: unify style and fix spelling

See merge request !13

The conventional approach for choosing an interpreter is based on
virtual environments.
Thus `/usr/bin/env python3` should be used instead of mixed shell/python
code for selecting a hard-coded interpreter.

Thanks, codespell!

These assignments caused style warnings (flake8).

The current target length is 99 characters.

Thanks, flake8.

The exceptions to be handled should be specified, otherwise even a
"NameError" would be caught.

Thanks, flake8.

Thanks, flake8.