fix(deps): update Effect to 3.22 and fix the new language-service errors

[GraemeF]

Takes Renovate's Effect 3 update from #388 and fixes what broke its build.

The newer Effect language service reports failing an Effect with a plain Error as a warning, and our tsc runs fail on it. Each such site now fails with a tagged error:

• Timeouts use Cause.TimeoutException, and "expected a value" checks use Cause.NoSuchElementException.
• The connection config layer reuses the existing ConnectionError.
• The todo example and the docs validation script each get one small Data.TaggedError.
• The todo example's ID parsers now return Schema's ParseError directly.

Public signatures are unchanged. The testing-contracts helpers still declare Error, and the changeset covers the new tags they fail with.

Postgres store fix. @effect/sql-pg 0.53 opens a new connection for its first LISTEN, where 0.49 reused a pooled one. That exposed a bug in our notification listener, which started LISTEN in the background and returned before it was active. Any event committed in that gap was lost, and the subscription tests failed in CI. listen and listenAll now wait until a probe notification sent to their own channel comes back. Every listener drops probe payloads. The probe goes through pg_notify, because the notify in @effect/sql-pg 0.53 sends a parameterised NOTIFY, which Postgres rejects. The two new tests in bridge.integration.test.ts fail against the old listener.

This also bumps @effect/language-service to 0.87.3. Once this merges, #388 can be closed.

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud