chore: publish new package versions (#3384)

This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.


# Releases
## @electric-sql/[email protected]

### Patch Changes

-   Updated dependencies [b377010]
    -   @electric-sql/[email protected]

## @electric-sql/[email protected]

### Patch Changes

-   Updated dependencies [b377010]
    -   @electric-sql/[email protected]

## @electric-sql/[email protected]

### Patch Changes

- b377010: Fix race condition where collections get stuck and stop
reconnecting after rapid tab switching, particularly in Firefox.

**Root cause:** Two race conditions in the pause/resume state machine:

1. `#resume()` only checked for `paused` state, but `#pause()` sets an
intermediate `pause-requested` state. When visibility changes rapidly,
`#resume()` is called before the abort completes, leaving the stream
stuck.
2. Stale abort completions could overwrite the `active` state after
`#resume()` has already started a new request.

    **State machine flow:**

        Normal pause:
          active → pause() → pause-requested → abort completes → paused

        Interrupted pause (rapid tab switch):
          active → pause() → pause-requested → resume() → active
                   ↑                              ↑
                   abort starts              resumes immediately,
                                             prevents stuck state

**Additional fix:** Memory leak where visibility change event listeners
were never removed, causing listener accumulation and potential
interference from stale handlers.

## @electric-sql/[email protected]

### Patch Changes

-   Updated dependencies [b377010]
    -   @electric-sql/[email protected]

## @core/[email protected]

### Patch Changes

- 58853d2: Remove shape storage metadata backup mechanism now that shape
lazy loading is in place.
- 2747a71: Reduce consumers to a single process instead of a supervisor
& children
- 6cbcbd6: Isolate call home reporter HTTP request to avoid interference
from HTTP pool messages.
- e04af96: Return 503 instead of 400 in case generated column
replication is not enabled for PG >=18.
- c4d0ea4: Update `otel_metric_exporter` dependency to fix issues with
event handler detachments.
-   55c7ca1: Speed up shape metadata removal
- 4036fb6: Ensure per-shape file operations do not go through Erlang
file server to avoid bottlenecks.
- 0c619e6: Support externally defined OTEL resource attributes in the
metrics exported from ApplicationTelemetry and StackTelemetry
- 4df1fba: Ensure async deletion requests don't clog up as removal is
taking place by moving removal to asynchronous task.
- e204906: Simplify API handling of snapshot errors that result in 503
responses.
- 68b686b: Avoid additionaly syscall when asynchronously deleting things
by assuming uniqueness with strong fallback.
- d413fc5: Ensure consumer registry does not crash on a lookup when
registry table is missing.
- 9eccb89: Allow snapshot query connection pool to queue up requests for
connections for longer to smoothen out bursts.
- 526e379: Fix incorrect run_queue_length metric definition that
prevented individual scheduler queue lengths from getting exported.
- f1a5f4f: Fix function arguments for
ShapeCache.start_consumer_for_handle/2
- 84c7119: Instrument publication relation updates with appropriate
telemetry.
- 766a375: Use longer timeout when waiting for snapshots to start in
requests.

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Author: github-actions[bot]