Enforce restrict-try-block lint rule

[rdlabo]

Summary

• enable @rdlabo/rules/restrict-try-block with the strict fleet defaults
• update @rdlabo/eslint-plugin-rules to 21.2.6 and align its Angular tooling dependencies
• replace broad async try blocks and Promise.resolve() escape hatches with explicit async boundaries
• preserve synchronous-throw handling for retry, queue, KV, and test database paths
• add regression coverage for synchronous handler, ack, retry, and KV failures

Why

The shared Workers toolkit should enforce the same narrow error-boundary policy as its consumers. Version 21.2.6 also rejects Promise.resolve() escape hatches, so existing code needed to express Promise rejection handling directly while retaining the synchronous failure behavior of the previous try blocks.

The plugin statically loads its Angular template rule without declaring the parser dependency, so the parser is declared explicitly. Angular peers are pinned to the 21.x toolchain, and their Node requirement is recorded separately in devEngines without narrowing the published runtime support.

Impact

There are no intended public API changes. Error handling remains fail-soft or retrying where it was before, including callbacks and bindings that throw before returning a Promise.

Validation

• npm ci
• npm run lint
• npm run typecheck
• npm test (64 files, 461 tests)
• npm run format:check
• npm run build
• git diff --check
• approved after iterative manager and independent third-party reviews

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 2 additional findings.