feat: Rhinestone Relay Provider

[yagopv]

Summary

This pull request updates the relay provider integration to use Rhinestone as the relay provider

Changes

Relay provider migration and configuration simplification:

• Updated .env.sample.json and configuration files to use a single RELAY_PROVIDER_API_KEY (project-level key) instead of per-chain keys, and changed the default relay provider base URI to Rhinestone (https://v1.orchestrator.rhinestone.dev). [1] [2]
• Updated the configuration schema and validator tests to expect only RELAY_PROVIDER_API_KEY instead of per-chain keys. [1] [2] [3] [4] [5]
• Simplified the relay.apiKey configuration from an object mapping chain IDs to keys, to a single string value. [1] [2]

Code and test updates:

• Added new rhinestone-api.service.ts using the Rhinestone API integration
• Updated the IRelayApi interface to allow an optional safeTxHash parameter in the relay method.
• Removed the now-obsolete gelato-api.service.spec.ts test file, which was specific to the old Gelato per-chain key setup.
• Added a new RELAY_SUPPORTED_CHAIN_IDS constant for use in relay tests, reflecting supported chains with the new project-level key approach.

[datadog-official]

⚠️ Warnings

🚦 1 Pipeline job failed

CI | biome     

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 124bdca | Docs | Give us feedback!}