Verify wheels-sentry@1.0.1 end-to-end on the engine matrix

[bpamiri]

Verification follow-up from wheels-dev/wheels#2738 — the design fix (plural `mappings` field) shipped in 83b679e (v1.0.1) plus framework #2705 / #2739, but the engine-matrix smoke test from the original issue body was not executed before #2738 was closed.

Verification checklist

• `wheels packages add wheels-sentry` against a fresh Wheels 4.0 app on each CI engine:
  • Lucee 6
  • Lucee 7
  • Adobe 2023
  • Adobe 2025
  • BoxLang
• Boot the app, trigger an error, confirm a Sentry event is emitted on each engine
• Confirm `application.sentry` initialized successfully on each engine (no silent `try/catch` swallow in `Sentry.cfc::initSentry()`)
• Confirm the `plugins.sentry` CFML mapping is registered at boot via `package.json`'s `mappings` field, not relying on the legacy `plugins/sentry/` install path

Why this matters

The fix path that shipped (Option 3 from #2738) depends on the framework's `PackageLoader` honoring the plural `mappings` field at boot and emitting a valid CFML mapping that survives across engines. Engine-specific quirks around `<cfapplication action="update" mappings="...">` (LDEV-2555 on Lucee, etc.) make smoke-testing on each engine the only durable confidence signal.

A Sentry DSN is required for the event-emission check — any free-tier project works.