Add peapods substream package

[DanailYordanov]

Peapods Swap Adapter Substreams Package

This PR integrates the swap adapter for peapods into tycho protocol's sdk. Following is the package overview -

Package Overview

The package consists of five core modules that work together to track and index protocol changes:

1. map_function_calls - Maps adapter contract function calls (Swap, SwapToPrice, Price) into structured FunctionCalls
2. store_exchange_price - Stores exchange prices from function calls in the store
3. map_token_pairs - Creates protocol components for token pairs based on function calls
4. store_token_pairs - Persists token pair protocol components in the store
5. map_protocol_changes - Aggregates changes from function calls and components into BlockChanges

Config Overview

Currently there are 2 config substreams.yaml files for the base network -

• substreams-legacy.yaml - This config file is for the legacy swap adapter contract that helps indexing it on base.
• substreams-new.yaml - This config file is for the new swap adapter contract implementation that helps indexing it on base.

The detailed overview of the package is also present in the README.md file.

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-	-	Generic High Entropy Secret	92df0f2	substreams/ethereum-peapods/substreams-new.yaml	View secret
-	-	Generic High Entropy Secret	92df0f2	substreams/ethereum-peapods/substreams-legacy.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}