Ensures that if `CryptoJS.AES.decrypt` fails (e.g., due to a bad
password), we throw an explicit error message rather than relying
on subsequent JSON parsing failure.

Exposes the `isLoading` status from `useLocalStorage` via
`useOtpParameters` to allow consumer components to handle
initial data hydration states properly.

Also integrates the global `Toaster` component for displaying
notifications across the application.

Extract `Encrypter` logic into `CryptoJsSerializer` to clean up the
`useOtpParameters` hook.

This commit also introduces the `WebCryptoSerializer` utility which
provides functions to decrypt data originally encrypted by CryptoJS
using the browser's native `window.crypto` methods (AES-CBC +
EVP_BytesToKey derivation).

This prepares the codebase for potentially migrating away from
`crypto-js`.

…storage

* 'main' of github.com:rm-hull/zaup2:
  refactor: Improve alert structure and data flow (#931)

Introduces robust error handling for data retrieval and decryption:

*   Displays an error toast notification if the OTP data fails to load
    in the UI (`Group.tsx`).
*   Catches decryption/parsing failures in `CryptoJsSerializer` and
    throws an error that includes the original exception as the cause,
    improving debugging capabilities.

Refactors the `WebCryptoSerializer` to track password verification
status.

- Serialization is blocked if the password previously failed
  decryption checks.
- Decryption failures now set the internal bad password state and
  throw a richer error.

Also, removed local error handling (toasting) in `<Group />` component
to ensure data loading errors are propagated via `throw error;` for
centralized error boundary management.

* 'main' of github.com:rm-hull/zaup2:
  chore: Update chakra-error-fallback dependency
  chore: Extract ErrorFallback to external lib
  refactor: Use standard `use-local-storage` hook (#930)
  feat: Enhance error fallback with source maps (#932)
  refactor(Redirect): Condense logic and return null

* 'main' of github.com:rm-hull/zaup2:
  chore: update yarn

Refactors the `evpBytesToKey` function in the WebCrypto serializer
to use synchronous MD5 hashing via CryptoJS internally. This ensures
key and IV derivation is identical to the standard OpenSSL
EVP_BytesToKey derivation used by CryptoJS, guaranteeing full
compatibility between both serializer implementations.

Adds comprehensive compatibility tests to verify bidirectional
serialization and deserialization between the two serializers.

The testing workflow is updated:
*   `test` now runs tests once (`vitest run`).
*   `test:watch` is introduced for watch mode (`vitest`).