feat(webmodeler): H2, MariaDB and MySQL configuration

[JacobiCamunda]

Description

Closes https://github.com/camunda/web-modeler/issues/18465

When should this change go live?

• This is a bug fix, security concern, or something that needs urgent release support. (add bug or support label)
• This is already available but undocumented and should be released within a week. (add available & undocumented label)
• This is on a specific schedule and the assignee will coordinate a release with the Documentation team. (create draft PR and/or add hold label)
• This is part of a scheduled alpha or minor. (add alpha or minor label) (8.9.0-alpha1)
• There is no urgency with this change (add low prio label)

PR Checklist

• The commit history of this PR is cleaned up, using {type}(scope): {description} commit message(s)

• My changes are for an upcoming minor release and are in the /docs directory (version 8.8 8.9).
• My changes are for an already released minor and are in a /versioned_docs directory.

• I added a DRI, team, or delegate as a reviewer for technical accuracy and grammar/style:
  • Engineering team review
  • Technical writer review via @camunda/tech-writers unless working with an embedded writer.

[github-actions]

👋 🤖 🤔 Hello, @christinaausley! Did you make your changes in all the right places?

These files were changed only in docs/. You might want to duplicate these changes in versioned_docs/version-8.8/.

• docs/reference/supported-environments.md
• docs/self-managed/components/modeler/web-modeler/configuration/configuration.md
• docs/self-managed/components/modeler/web-modeler/configuration/database.md

You may have done this intentionally, but we wanted to point it out in case you didn't. You can read more about the versioning within our docs in our documentation guidelines.

[JacobiCamunda]

@camunda/tech-writers, I did not add the 8.9.0-alpha1 label because it currently does not exist and I didn't know if it is okay for me to just create or there is some kind of automation or similar.

Also, could you take a look if the database.md custom databases part should be overhauled with the bigger amount of vendors now? I am also fine if this is good enough for customers. For example, the case-sensitive part for some vendors is very similar often times. But this can also be a follow-up.

@aleksander-dytko, I added you like last time as reviewer to make sure I didn't oversee anything.

@Szik, I also added you for the setup part, because I got the test setup from you and reused some of it and I know it can be improved.

[mesellings]

@christinaausley I've assigned to you for review as I think this probably relates to your database docs work?

[jfriedenstab]

Looks good! Just two minor comments.

[christinaausley]

@JacobiCamunda I'll give this a final review after comments are resolved from @Szik to avoid making things messy 👍

[JacobiCamunda]

@christinaausley, I addressed all comments from @Szik. You can give your final review. @aleksander-dytko, feel free to also add your feedback. If not, the PR is ready to merge after I then addressed @christinaausley's comments.

[christinaausley]

@JacobiCamunda Feel free to review my latest commit with all of my adjustments and let me know if you have questions 🚀

[github-actions]

The preview environment relating to the commit 45f97e6 has successfully been deployed. You can access it at https://preview.docs.camunda.cloud/pr-7208/