Track and retry pending benchmarks

[Y3drk]

Goal

Keep track of the benchmarks that couldn't be completed for any reason, and retry once the blocker is dealt with.

NOTE:

• The majority of benchmarks from contract-naming best practice category are still pending due to the category content being unfit for presentation.
• Because this category is not publicly available for now, I won't add them to the list.
• Once the category and its best practices are healed, I'll benchmark what I can and add still-pending elements to the list

Still pending benchmarks

Pending benchmark (App, best practice, acceptance test)	Reason	Completed	How was the blocker solved?
coinbase-exchange, deposit-addresses, AT6 (Bitcoin)	Insufficient funds to test in the "send" flow	❌	-
cryptocom-wallet, deposit-addresses, AT6 (Bitcoin)	Insufficient funds to test in the "send" flow	❌	-
whitebit-exchange, deposit-addresses, AT6 (Bitcoin)	Insufficient funds to test in the "send" flow	❌	-
whitebit-exchange, deposit-addresses, AT7 (Solana)	Insufficient funds to test in the "send" flow	❌	-

[coderabbitai]

🔗 Related PRs

#232 - feat: Add new apps tranche3 [merged]
#233 - dev: Add deposit-address best practice [merged]
#235 - feat: ATs for blockscout and 1inch [merged]
#237 - feat: add builders for notes to decrease boilerplate [merged]
#247 - feat: Benchmark wallets on deposit-addresses best practice, batch 3 [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!