chore: update nostr notification provider

[zappityzap]

⚠️⚠️⚠️ Since we do not accept all types of pull requests and do not want to waste your time. Please be sure that you have read pull request rules:
https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma

Tick the checkbox if you understand [x]:

• I have read and understand the pull request rules.

Description

• Update nostr-tools to 2.10.4
• Support relays that require AUTH like auth.nostr1.com
• Tested with Node 18, 20 and 22

Type of change

Please delete any options that are not relevant.

• New feature (non-breaking change which adds functionality)

Checklist

• My code follows the style guidelines of this project
• I ran ESLint and other linters for modified files
• I have performed a self-review of my own code and tested it
• I have commented my code, particularly in hard-to-understand areas (including JSDoc for methods)
• My changes generates no new warnings
• My code needed automated testing. I have added them (this is optional task)

Screenshots (if any)

Event	After
UP
DOWN
Certificate-expiry
Testing

[CommanderStorm]

About this PR:
What is the motivation?
Is this breaking for existing users?

[zappityzap]

Main motivation is to get the library updated since the protocol is evolving quickly. There's a newer method for sending direct messages with better privacy that I'd like to implement, but it's not widely supported yet, and it requires a newer library.

Additionally, some public relays require a sender to respond to an AUTH challenge before accepting a direct message event to reduce potential spam. This PR enables responding to those AUTH challenges, making it easier to use this notification provider.

[CommanderStorm]

Is this breaking for existing users?

[zappityzap]

Sorry, I didn't understand the question at first. This doesn't break anything for existing users.