Make password and user name requirements configurable

Summary

Fix caosdb/customers/leibniz-zmt/management#95 Implement caosdb/customers/leibniz-zmt/management#94

See also: #121 (closed)

Focus

Point the reviewer to the core of the code change. Where should they start reading? What should they focus on (e.g. security, performance, maintainability, user-friendliness, compliance with the specs, finding more corner cases, concrete questions)?

Test Environment

How to set up a test environment for manual testing?

Check List for the Author

Please, prepare your MR for a review. Be sure to write a summary and a focus and create gitlab comments for the reviewer. They should guide the reviewer through the changes, explain your changes and also point out open questions. For further good practices have a look at our review guidelines

• All automated tests pass
• Reference related issues
• Up-to-date CHANGELOG.md (or not necessary)
• Annotations in code (Gitlab comments)
  • Intent of new code
  • Problems with old code
  • Why this implementation?

Check List for the Reviewer

• I understand the intent of this MR
• All automated tests pass
• Up-to-date CHANGELOG.md (or not necessary)
• The test environment setup works and the intended behavior is reproducible in the test environment
• In-code documentation and comments are up-to-date.
• Check: Are there specifications? Are they satisfied?

For further good practices have a look at our review guidelines.

doc/devel/Benchmarking.md

@@ -59,7 +59,10 @@ enabled on start up.
 This script expects the MariaDB server to be accessible on 127.0.0.1 with the default caosdb user
 and password (caosdb;random1234).
 
-
+You might consider to increase `performance_schema_events_transactions_history_long_size`.
+```
+performance_schema_events_transactions_history_long_size=1000000
+```
 The performance schema must be enabled (see below).
 
 ### MariaDB General Query Log ###