feat(service): add uptime kuma with mariadb template

[piscis]

Changes

• feat(service): add uptime kuma v2 with mariadb template

Considerations

• I decided not to generate a db-config.json via Docker Compose. Users must deploy the service first and then configure it through the web interface. This might be worth adding to the documentation.
• Although Uptime Kuma v2 supports an internal MariaDB instance, I chose to use an external container so users can leverage Coolify’s built-in backup functionality for the database.
• I’m unsure whether we should provide a default custom MariaDB configuration. I kept the settings and tweaks to a bare minimum for now.

[ShadowArcanist]

Holding this due to https://github.com/louislam/uptime-kuma/wiki/Migration-From-v1-To-v2#docker-only-breaking-changes

Will circle back to this PR once moby/moby#40734 is closed

[github-actions]

Hi @piscis! 👋

It appears to us that you are either adding a new service or making changes to an existing one.
We kindly ask you to also review and update the Coolify Documentation to include this new service or it's new configuration needs.
This will help ensure that our documentation remains accurate and up-to-date for all users.

Coolify Docs Repository: https://github.com/coollabsio/coolify-docs
How to Contribute a new Service to the Docs: https://coolify.io/docs/get-started/contribute/service#adding-a-new-service-template-to-the-coolify-documentation

[peaklabs-dev]

Thanks for the PR.

I removed the custom config for mariadb and added uptime kuma v2 with mysql to the next version as well.