Release Megaphone 1.1.0 with durable notifications and recipient inbox APIs

[elpete]

This adds the notification inbox, preferences, durable delivery, and web push work for Megaphone 1.1.0. It also changes the package version from 1.1.0-rc.1 to 1.1.0 so we can release it as stable.

You can keep using the existing notification and provider APIs. The new features add read/archive state, history imports, preferences by scope and channel, per-device push subscriptions, and stored delivery attempts with retries and operator recovery. The docs cover the migrations and the callbacks your app needs to supply.

Installing the module won't move existing history or pending deliveries over for you. You'll need to apply the migrations and plan the handoff from your current delivery owner. Push also needs encryption keys, credentials, the optional SDK, and your browser/service-worker setup.

The CI fixes also cover MySQL timestamp rounding, Adobe receipt decisions and Java reflection, and optional database settings on Lucee. The test harness now uses the right module mapping, installs the SDK, and runs against MySQL. Apply the new delivery timestamp migration along with the other migrations.

The separate GitBook docs are updated in docs PR #1.

Validation

• 198 tests passed locally on Lucee 5 and Adobe 2023 with ColdBox 6 and MySQL, and 202 passed on both engines with ColdBox 7. Adobe retained four existing ColdBox 6 skips.
• The MySQL migrations passed a full rollback and reapplication. The 69 PostgreSQL database and preference checks passed too.
• Formatting, whitespace checks, and local archive content checks passed.
• All eight CI test jobs pass on the latest commit: Lucee 5/6 and Adobe 2021/2023, each with ColdBox 6/7. The inbox and dispatcher specs also passed independently before any legacy module setup.
• Formatting passed in both workflows. The PR format job passed on retry after a ForgeBox download timeout.

These tests don't send to real providers. Actual push providers and devices, clean installation of this stable candidate, and deployment still need verification.

Merging to main runs the existing tests and semantic-release workflow. Nothing has been published yet, and CommuniArts still uses the RC. Check ForgeBox publication before changing that pin.