feat: Solana integration roadmap task

[subbareddypalagiri]

Hey team!

I've taken a deep dive into the exciting challenge of integrating our 'Saver' functionality with the Solana Network, as outlined in the bounty issue. It's a fantastic goal, and I'm thrilled to lay down the groundwork for it!

As we know, our current codebase is built on the EVM (Ethereum Virtual Machine) with Hardhat, while Solana operates on a completely different architecture (Rust-based programs, Sealevel VM). This means a direct "port" isn't feasible.

My approach to solving this issue, given the architectural differences and the significant bounty, is to provide a clear, strategic roadmap and initial conceptual framework within our existing Hardhat project.

This PR introduces a new Hardhat task, solana-integration-roadmap, which you can run via npx hardhat solana-integration-roadmap. This task:

1. Explains the EVM-Solana architectural differences: Setting the stage for why a direct port isn't possible.
2. Proposes two main integration paths: Cross-chain bridging (recommended for interaction) or full re-implementation (for a standalone Solana version).
3. Details initial actionable steps for a bridging approach: This includes defining cross-chain interfaces, selecting a bridge protocol, and conceptualizing EVM-side bridge integration (e.g., interfaces, mock contracts, and calls from Forge.sol). It also highlights the need for a separate Solana program development project.

This task serves as a crucial first step, providing the necessary clarity and direction for tackling this complex cross-chain integration. It ensures we're all on the same page regarding the architectural challenges and the strategic path forward, making the $15000 bounty a well-deserved investment in our project's multi-chain future.

I believe this is the most effective way to address the issue within the scope of this repository, offering a concrete plan rather than an impossible code change.

Looking forward to your thoughts and collaborating on this!

Fixes #4