data(tatum): link current pricing and plan docs

[nwinkelman2]

Summary

• replace generic Tatum homepage purchase links on the six paid canonical API plans with the live pricing surface while preserving the Chain.Love referral parameter
• replace generic documentation links on those plans with Tatum's current Plans & Limits documentation
• route the 12 paid Algorand mainnet/testnet listings to the same current pricing surface while retaining the exact Algorand RPC reference

Official sources

• https://tatum.io/pricing?via=chainlove
• https://docs.tatum.io/docs/plans-limits
• https://docs.tatum.io/reference/rpc-algorand

Validation

• all three official URLs return HTTP 200
• API offer CSV: 390 rows, 390 unique slugs, 28 columns
• Algorand API listing CSV: 77 rows, 77 unique slugs, 29 columns
• exactly 18 paid Tatum records now use the current pricing path
• all JSON-valued fields parse successfully
• all listing offer references resolve
• both edited CSVs remain A-Z sorted by slug
• live open-PR search found no Tatum pricing/link overlap; data(algorand): add verified Tatum SDK links #3001/data(algorand): add verified MCP action links #3003/feat(sdks): fill vendor SDK metadata from each row's own documented package #3233 modify SDK/MCP data only, while data(algorand): add Nodely Business API plans #3443/data(algorand): link official API resources #3452 modify different API rows
• git diff --check passes
• commit includes DCO sign-off

The contributor reward address remains pending owner confirmation; no address has been invented or inferred.

---

Reward address (USDC/USDT, Ethereum mainnet): 0xd2b19220877be4d3ff5c51a99b63c545ad73101f

[github-actions]

Summary

Status	Count
🔍 Total	4
🔗 Unique	3
✅ Successful	4
⏳ Timeouts	0
🔀 Redirected	0
👻 Excluded	0
❓ Unknown	0
🚫 Errors	0
⛔ Unsupported	0

Full Github Actions output

[USS-Supervisor]

Verdict: APPROVE
Risk: LOW
Summary: Required validation is passing, the current-cycle link-check completed successfully with zero reported errors/timeouts/unsupported links, and the changed CSV data keeps valid widths with resolving references.
Findings: None.
Confidence: HIGH

[USS-Supervisor]

Hi @eugene17kotov - this PR is stale, required CI is passing, and I do not see a current creator-side blocker. I requested your review; could you please take a look when you have a chance?