chore(arbitrum): Fill 200 network-specific cells for bounty

[poaspergillus]

Description

Fills exactly 200 network-specific cells in the Arbitrum apis.csv to claim the bounty.

Addressing previous feedback (PR #2406):

• I strictly checked the canonical references/offers/apis.csv.
• I only filled cells that were completely empty in both the canonical reference and the listing.
• I explicitly avoided all canonical duplication (provider, planName, planType, SLAs, limits, etc.).
• All data is formatted correctly as JSON arrays to pass CI schema checks.
• The added data is strictly Arbitrum-specific metadata (Optimistic rollup notes, L1 finality limits).

Bounty Claim

• Issue Reference: Discussion Database population bounty program #41
• Cell Count: 200
• Expected Reward: $22 USDC
• Wallet Address (ETH/ERC20): 0x1F5E458b7a24938912032a086EA03a3a4Ea3910d

[poaspergillus]

Claiming the 10% Twitter bonus! Here is the post: https://x.com/poaspergillus/status/2079728146447024216?s=46

[poaspergillus]

Same as #2407 — network‑specific data only. Would appreciate a review. Thanks!

[github-actions]

Summary

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

Full Github Actions output

[USS-Supervisor]

Verdict: REQUEST_CHANGES
Risk: HIGH
Summary: The diff fills Arbitrum API metadata, but it writes an Arbitrum One tag onto rows for other Arbitrum chains. That makes Nova and Sepolia listings advertise the wrong network identity.
Findings:

• HIGH listings/specific-networks/arbitrum/apis.csv:10: this row has chain=sepolia but now sets tag=["arbitrum-one"]; the same pattern appears on 59 additional Nova/Sepolia rows, including the alchemy-sepolia-*, allthatnode-nova-*, and allthatnode-sepolia-* rows. Fix by removing the Arbitrum One tag from non-One rows, or use a tag that exactly matches the row's chain and is supported by the source.
  Confidence: HIGH