data(providers): fill missing contact and social fields (batch 2)

[EazyHood]

Fills empty contact and social fields in references/providers/providers.csv from each provider's
own site and documentation. No existing values were changed; only empty cells were populated.

Rewards address

0x06f44f4839fd5df4f4670036d028b29dec939363

[github-actions]

Summary

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

Errors per input

Errors in ./references/providers/providers.csv

• [ERROR] https://developers.swing.xyz/ (at 105:1) | Connection failed. Check network connectivity and firewall settings
• [ERROR] https://swing.xyz/ (at 104:1) | SSL certificate error. Check certificate validity
• [404] https://x.com/mimic_fi (at 224:1) | Rejected status code: 404 Not Found

Full Github Actions output

[USS-Supervisor]

Verdict: REQUEST_CHANGES
Risk: HIGH
Summary: The provider CSV still parses and required validation passed, but this PR introduces destructive provider-row churn outside the stated contact/social fill scope.
Findings:

• HIGH references/providers/providers.csv rows 150, 259, 262, and 456: the PR removes the canonical provider rows for cidgravity, fil-one, filecoin-onchain-cloud, and palmera that are present on current main. Please rebase/restore these provider records so the PR only fills empty provider metadata cells.
  Confidence: HIGH

[EazyHood]

Fixed. The branch is now rebased onto current main, so the four provider rows that were reported as
removed — cidgravity, fil-one, filecoin-onchain-cloud and palmera — are present and byte-identical
to main. The diff is now symmetric and contains only the filled contact cells.

The flagged social handles have been cleared rather than guessed. I also re-checked every value this
PR adds rather than only the ones you flagged: all X handles and Discord invites resolve, and for
Telegram I compared each channel's own title against the provider instead of only checking that the
link loads. That surfaced one more bad handle you had not flagged — blueprint pointed at a channel
titled "QDev Studio" — which is now cleared too.

[USS-Supervisor]

@eugene17kotov This PR has passing required CI and is waiting on reviewer action. Could you please take a look when you have a chance?

[EazyHood]

The changes requested here have been addressed in the latest push. Could you take another look when you get a chance?