fix(notifications): add missing serverThreshold for gotify/ntfy and f…

[abhi128nandan]

What is this PR about?

This PR fixes two separate issues with the server threshold notification system. First, it adds the missing serverThreshold property to the Gotify and Ntfy schemas, service insert/update functions, and frontend UI forms so the preference correctly persists to the database. Second, it moves the Teams notification dispatch in server-threshold.ts inside the try/catch error boundary to prevent an unhandled rejection from aborting the entire notification processing loop.

Checklist

Before submitting this PR, please make sure that:

• You created a dedicated branch based on the canary branch.
• You have read the suggestions in the CONTRIBUTING.md file
  https://github.com/Dokploy/dokploy/blob/canary/CONTRIBUTING.md#pull-request
• You have tested this PR in your local instance. If you have not tested it yet, please do so before submitting. This helps avoid wasting maintainers' time reviewing code that has not been verified by you.

Issues related (if applicable)

closes #5175

Screenshots (if applicable)

(No visual UI changes, just backend persistence/error boundary fixes)

Greptile Summary

This PR completes Gotify and Ntfy server-threshold persistence across the UI, API schema, and notification services, and moves Teams delivery inside the notification loop’s error boundary.

• Passes serverThreshold through Gotify and Ntfy form initialization and mutation payloads.
• Accepts and persists the flag in Gotify and Ntfy create/update paths.
• Contains Teams delivery failures within the existing per-notification error handler.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

_{Reviews (3): Last reviewed commit: "Merge branch 'Dokploy:canary' into fix/g..." | Re-trigger Greptile}

[abhi128nandan]

Hi @Siumauricio, could you please take a look at this PR when you get a chance? Thanks! 🙏