Modify CircuitBreaker and RateLimit registries to improve ETS table
resilience. ETS tables are now created with an heir process, defaulting to
the :init process. This prevents the loss of state and telemetry data if
the process that originally created the table terminates.

In the CircuitBreaker registry, added logic to validate the state of tables
retrieved from :persistent_term. The registry now checks if the table
exists and ensures its assigned heir is still alive. If the cached table
reference is invalid, a new registry is automatically created and stored.

These updates include adding a helper to resolve the :init process as
a stable heir and updating table creation to include the :heir option in
both modules. This ensures that the underlying storage remains available
across process restarts within the application supervision tree.