fix: accept the mixed-case keys Pushover issues

Pushover application tokens and user keys are 30 characters from a
case-sensitive alphanumeric alphabet, but both fields were validated
against /^[a-z0-9]{30}$/. A key containing a single capital - which is most
of them - could not be saved at all: the field stayed outlined in red and
the integration could never be created.

The workaround reporters arrived at was to lowercase their own key, which
is not the same key and names a different account, so the integration then
saved and silently delivered nothing.

Both fields move together, as they share the same alphabet.

Fixes #726

Author: i7Gamer

server/integrations/pushover.js

@@ -25,8 +25,8 @@ export default (registerEvent) => {
     return {
         icon: "fa-solid fa-pushover",
         fields: [
-            {name: "token", type: "text", required: true, regex: /^[a-z0-9]{30}$/},
-            {name: "user_key", type: "text", required: true, regex: /^[a-z0-9]{30}$/},
+            {name: "token", type: "text", required: true, regex: /^[A-Za-z0-9]{30}$/},
+            {name: "user_key", type: "text", required: true, regex: /^[A-Za-z0-9]{30}$/},
             {name: "send_finished", type: "boolean", required: false},
             {name: "finished_message", type: "textarea", required: false},
             {name: "send_failed", type: "boolean", required: false},