Hebrew translation + notification action buttons, opt-in prompt, Safari/iOS support

[ClickAndGoScript]

This PR started as Hebrew (he) translation support and grew while I was running the plugin on my own forum. What it contains now:

• Hebrew translation, plus the missing zh-CN strings
• "Mark as read" / "View notifications" action buttons on push notifications
• An optional banner suggesting users enable push notifications — off by default, with an ACP setting for how many page visits before it shows
• Service worker registration on Safari/iOS (16.4+), where core skips it, plus fixes to the settings page so it doesn't hang when no SW is registered
• All remaining hardcoded strings (ACP page, admin menu item, test notification) moved to the language files

Known limitation: on Safari/iOS, older notifications with the same tag aren't cleared when a new one arrives, so users can end up with a few notifications with overlapping content. Details in the comments.

The commit history is messy — best to review the full diff.

[julianlam]

Ah... A lot is going on here.

@ClickAndGoScript are you looking to just add the translations?

[ClickAndGoScript]

@julianlam yeah, sorry about that :) It did start as just the translations, but I've been running the plugin on my own forum since then and kept pushing fixes and features to the same branch. The commit history ended up messy (experiments, reverts, merge commits), so it's best to review the full diff and ignore the individual commits. I've updated the PR title and description to reflect what's actually in here now.

What's in here besides the Hebrew translation:

• Action buttons on push notifications: "Mark as read" and "View notifications". Mark as read works from the service worker itself, since there's usually no forum tab open when you tap a push notification.
• An optional banner suggesting users enable push notifications, shown to logged-in users after X page loads. Off by default, configurable in the ACP, and dismissing it is remembered per device so it won't nag.
• Service worker registration on Safari/iOS. Core skips SW registration on Safari, which predates iOS 16.4 where push is actually supported now, so the plugin registers it itself. Also fixed the settings page hanging forever on serviceWorker.ready when no SW is registered.
• Moved the remaining hardcoded strings (ACP page, admin menu item, test notification) into the language files, so the test notification arrives translated too. Added the missing zh-CN strings while at it.

One known limitation I couldn't solve: on Safari/iOS, older notifications aren't cleared when a new one with the same tag arrives. To be clear, nothing arrives twice - every notification shows up exactly when it should. It's just that when notifications share a tag (e.g. consecutive chat messages that get merged), the new one is supposed to replace the old one, and on Safari the old ones stay, so the user can end up with a few notifications stacked up with overlapping content. I tried the Topic header (apns-collapse-id) route, it didn't work, so I removed that code. Still better than the current state, where Safari users get no notifications at all.

If you'd rather take just the translation and have the rest split into separate PRs, no problem, let me know.

[julianlam]

Yes, the problem here is the commit history is messy so I would squash+merge but I prefer to rebase+merge.

Are you able to get claude (or whatever AI you use) to split this PR into four?

[ClickAndGoScript]

Okay, I'll try to split it up.
Actually, I already did a more organized restoration of the commits, but since the PR was still open since I opened it previously for the translations, it just made more of a mess (in the PR, not in my code, so it wouldn't be too difficult for me to reopen it in an organized way).

[julianlam]

It may be easiest for you to instruct the LLM to create new branches for each feature (translations, action buttons, opt-in prompt, Safari/iOS support)

Then it won't interfere with your existing branch that you use in your site.

[ClickAndGoScript]

I don't think these additions are extensive enough to allocate a separate branch to each of them, but I might actually do everything in the dev branch.