Track files on disk

[CBroz1]

Description

In a series of related efforts to manage disk space, I have set up infrastructure for ...

• Tracking of rec files
• Tracking of broken nwb files

Ideally, these steps would be integrated in existing maintenance cron jobs, but how much of this is specific to the Frank Lab versus generalization to some degree? Should these operations instead run from a separate repository in our weekly cleanups?

Checklist:

• If this PR should be accompanied by a release, I have updated the CITATION.cff
• If this PR edits table definitions, I have included an alter snippet for release notes.
• If this PR makes changes to position, I ran the relevant tests locally.
• If this PR makes user-facing changes, I have added/edited docs/notebooks to reflect the changes
• I have updated the CHANGELOG.md with PR number and description.

[codecov]

Codecov Report

❌ Patch coverage is 0% with 302 lines in your changes missing coverage. Please review.
✅ Project coverage is 68.86%. Comparing base (594bc98) to head (c7352f4).
⚠️ Report is 1 commits behind head on master.

Files with missing lines	Patch %	Lines
src/spyglass/common/common_file_tracking.py	0.00%	302 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1431      +/-   ##
==========================================
- Coverage   70.50%   68.86%   -1.65%     
==========================================
  Files         104      105       +1     
  Lines       12655    12957     +302     
==========================================
  Hits         8923     8923              
- Misses       3732     4034     +302     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.