Update "Data Retention" to "Storage Proving"

[nalacateria]

https://github.com/FilOzone/dealbot/blob/main/docs/checks/data-retention.md#why-is-this-called-data-retention-vs-data-availability

Right now, the top-level metric around "retention" implies data loss / deletion in the context data is not "retained" -- however the metric is actually measuring proving reliability, where gaps could indicate node uptime or proving ability instead of data retention. Instead of using the word "retention", we should use a word that more clearly maps to "proving" since that is the onchain process that is being measured and sets a clearer auditor expectation on network and SP health.

[BigLep]

The mis-branding makes sense sense. Calling it "Storage Prooving" sounds good. I assume we want it so that when someone goes to https://probelab.io/filecoin/foc/, that they see these three things:

• Data Storage
• Retrieval
• Storage Proving

Specificaly, I think this work is needed:

• https://github.com/FilOzone/dealbot/blob/main/docs/checks/data-retention.md
  • Rename it to the "Storage Proving" check throughout.
  • Add an FAQ entry explain why we call it "Storage Proving" instead of "Data Retention" check now.
  • We can leave the file as data-retention.md since there are various things that link to it.
• https://github.com/FilOzone/dealbot/blob/main/docs/checks/production-configuration-and-approval-methodology.md
  • "Data Retention" → "Storage Proving"
• I don't think we make any internal code changes/renames about this.
• Update verbiage on https://probelab.io/filecoin/foc/

[silent-cipher]

I have raised a PR #669 that renames "Data retention" to "Storage Proving". With this, I've also renamed "Data retention" occurrences in both betterstack dashboards. Remaining task:

• Update verbiage on https://probelab.io/filecoin/foc/