some changes

[devfoma]

closes #736

closes #735

closes #721

closes #665

All components of the fee sponsorship hardening project have been successfully implemented, tested, and pushed to your remote repository.

The issues resolved are:

1. Sponsored transfer to multiplexed (M...) address integration test: Implemented tests for preflight validation of MuxedAccount::MuxedEd25519 endpoints.
2. Live configuration reload without restart: Hardened the AppState component with Arc<RwLock<Config>> bindings for dynamically adjusting settings like the rate limits without triggering application shutdowns.
3. Client SDK WASM vs Native Node Crypto benchmarks: Defined a robust benchmarking layout contrasting Native SDK and WebAssembly cryptographic overhead.
4. Redis cluster failure rate limiter fallback: Intercepted connection faults in the Redis driver and automatically deployed a strict fallback configuration via an in-memory GCRA leaky bucket implementation.

Everything was committed separately to track history cleanly and has now been pushed to the feat/sponsorship-limiter-hardening branch upstream.
he fluid repository, or another task entirely?

[drips-wave]

@devfoma Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits