feat(notification): add Jira Service Management as a notification provider

[jankal]

Summary

In this pull request, the following changes are made:

• Implementation of a notification type for Jira Service Management as Opsgenie is replaced by JSM
• Resolves Update metrics' labels on saving an monitor. #6071

Claude Opus 4.5 was used to create this PR.

Please follow this checklist to avoid unnecessary back and forth (click to expand)

• ⚠️ If there are Breaking change (a fix or feature that alters existing functionality in a way that could cause issues) I have called them out
• 🧠 I have disclosed any use of LLMs/AI in this contribution and reviewed all generated content.
  I understand that I am responsible for and able to explain every line of code I submit.
• 🔍 Any UI changes adhere to visual style of this project.
• 🛠️ I have self-reviewed and self-tested my code to ensure it works as expected.
• 📝 I have commented my code, especially in hard-to-understand areas (e.g., using JSDoc for methods).
• 🤖 I added or updated automated tests where appropriate.
• 📄 Documentation updates are included (if applicable).
• 🧰 Dependency updates are listed and explained.
• ⚠️ CI passes and is green.

Screenshots for Visual Changes

[github-actions]

Hello and thanks for lending a paw to Uptime Kuma! 🐻👋
As this is your first contribution, please be sure to check out our Pull Request guidelines.
In particular: - Mark your PR as Draft while you’re still making changes - Mark it as Ready for review once it’s fully ready
If you have any design or process questions, feel free to ask them right here in this pull request - unclear documentation is a bug too.

[autofix-ci]

Hi! I'm autofix.ci, a bot that automatically fixes trivial issues such as code formatting in pull requests.

I would like to apply some automated changes to this pull request, but it looks like I don't have the necessary permissions to do so. To get this pull request into a mergeable state, please do one of the following two things:

1. Allow edits by maintainers for your pull request, and then re-trigger CI (for example by pushing a new commit).
2. Manually fix the issues identified for your pull request (see the GitHub Actions output for details on what I would like to change).

[CommanderStorm]

Mostly LGTM.
I have 2-3 questions about translations.

Please post the screenshots that we request in the contribution guide to ensure that you tested it working as expected.
I don't use/pay for Jira and don't want to set it up/pay for just for this PR. Hope you understand 😉

[jankal]

First, the screenshots @CommanderStorm

Event	Screenshot
UP
DOWN
Certificate-expiry
Domain-expiry	??
Testing

[jankal]

@CommanderStorm as you see, I was unable to create a screenshot for domain expiry. The guide asks to use google.com and set a larger notification time. I tried, but I never got a notification.
How do I make this send a domain expiry notification?

[jankal]

@CommanderStorm updated the UI (mainly to put the docs link at the right place):

[CommanderStorm]

Thank you, LGTM 👍🏻

[github-actions]

@jankal congrats on your first contribution to Uptime Kuma! 🐻
We hope you enjoy contributing to our project and look forward to seeing more of your work in the future! If you want to see your contribution in action, please see our nightly builds here.