feat(symbolConverter): add hip4 recurring outcome support

[vtx100]

Description of the Desired Feature
This PR introduces support for both priceBinary and priceBucket recurring outcomes inside the symbolConverter. It adds full support for generating slugs (identical to the ones used for web URLs) and mapping them to their corresponding assetIds, in accordance with the Hyperliquid documentation for Asset IDs and Contract Specifications.

Motivation and Use Case
Provide a standardized and human friendly way of retrieving assetIds (and eventually other information) about the new HIP4 outcome markets using the hyperliquid URL slug format.

Proposed Solution
I introduced the main orchestrator: _processAllRecurringAssets (which can be easily isolated or toggled via a flag if required). This orchestrator delegates to specific processors depending on how the market data is structured:

• _processBinaryOutcomeAssets: Handles binary markets where data is provided directly inside the outcomes field of outcomeMeta.
• _processRecurringBucketOutcomeAssets: Handles multi-price bucket markets. Because bucket responses are standardized, this processor iterates through the questions field and maps the namedOutcomes array to the corresponding entries inside the outcomes array. This makes it straightforward to generate all possible slugs.

Additional Information
Testing limitations: There currently isn't an easy way to write static tests for this feature because the slugs dynamically change based on the day/month. Additionally, the testnet does not provide fixed, long-term markets to test against, so validation requires separate handling.

Scope of the implementation: Support is currently limited to the officially documented recurring outcome markets (so what mainnet does). It does not handle non-standardized testnet cases (for example, the market "What will Hypurr eat the most of in May 2026?", where the name field contains the actual question rather than "Recurring"). These non-standard cases will require separate handling.

Extra: There doesn't seem to be a way to retrieve the getSzDecimals value for a given token, however this seems to be 5 for all markets (which would make sense, considering the nature of the markets), however i've decied not to hardcode this as it doesn't seem to be specified anywhere.

Below is attached a screenshot of the slug->asssetId mapping for currently avaialble mainnet markets: