161 booelan handling in sqlite

[LukasFehring]

As mentioned in the linked issue, this MR aims to solve the problem that booelans are currently added as strings into the db

Description

Adding values into the database is currently handled by the same function for both sqlite and MySQL. This is adapted to use an abstract function with separate implementations because of the different types.

Motivation and Context

Cuirrently sqlite writes booleans as strings into the db

Type Of Changes

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

How has This Been Tested?

• Database provider:
• Python version:
• Operating System:

Does this Close/Impact Existing Issues?

• Issue #161 is closed by this issue

What is Missing?

Checklist

• [x] My change is based on the latest stage of the develop branch.
• [ ] My change required a change of the documentation, which has been done.
• [x] I checked that the documentation can be build, visualizes everything as expected, and does not contain any warnings.
• [x] I have added/adapted tests to cover my changes.
• [x] The tests can be executed successfully.
• [x] The notebooks can be executed successfully.
• [x] The notebooks can be executed with mysql as provider.
• [ ] I have added a description of the changes to CHANGELOG.rst.