Add CryptoCompare Provider With Crypto Historical Support

[osasisorae]

I introduced an openbb-cryptocompare extension (pyproject, README, plugin wiring) because we needed a first-party provider that follows the documented structure.

I implemented CryptoCompareCryptoHistoricalFetcher covering 1m–1d intervals, VWAP/base-volume fields, and credential handling so users can query standardized OHLCV data from CryptoCompare.

I updated the root providers README to mention CryptoCompare so contributors know it exists.

I added a deterministic pytest that mocks the HTTP helper because we don’t have stable network access in CI.

I ignored .openbb_platform/ in .gitignore because openbb-core writes settings there during tests.

Tests: test_cryptocompare_fetchers.py.

issue #7177

[CLAassistant]

All committers have signed the CLA.

[deeleeramone]

Hi, thanks for the PR. Did you mean, Coindesk? CryptoCompare does not appear to be a valid API.

[osasisorae]

Thanks for flagging this. The implementation does target CryptoCompare’s REST API, and the endpoint still responds to calls like https://min-api.cryptocompare.com/data/v2/histoday?fsym=BTC&tsym=USD. That said, the bottom of their portal now shows a banner (“We’ve migrated our accounts and authentication to CoinDesk”), so it looks like account management is moving under CoinDesk even though the CryptoCompare hostname keeps serving data. Let me know if you’d prefer I rebrand the provider (or wire it directly to CoinDesk’s new auth flow) and I can update the PR accordingly.