Add seed file support to Browsertrix backend

[tw4l]

Fixes #2673

Changes in this PR:

• Adds a new file_uploads.py module and corresponding /files API prefix with methods/endpoints for uploading, GETing, and deleting seed files (can be extended to other types of files moving forward)
• Seed files are supported via CrawlConfig.config.seedFileId on POST and PATCH endpoints. This seedFileId is replaced by a presigned url when passed to the crawler by the operator
• Seed files are read when first uploaded to calculate firstSeed and seedCount and store them in the database, and this is copied into the workflow and crawl documents when they are created.
• Logic is added to store firstSeed and seedCount for other workflows as well, and a migration added to backfill data, to maintain consistency and fix some of the pymongo aggregations that previously assumed all workflows would have at least one Seed object in CrawlConfig.seeds
• Seed file and thumbnail storage stats are added to org stats
• Seed file and thumbnail uploads first check that the org's storage quota has not been exceeded and return a 400 if so
• A cron background job (run weekly each Sunday at midnight by default, but configurable) is added to look for seed files at least x minutes old (1440 minutes, or 1 day, by default, but configurable) that are not in use in any workflows, and to delete them when they are found. The backend pods will ensure this k8s batch job exists when starting up and create it if it does not already exist. A database entry for each run of the job is created in the operator on job completion so that it'll appear in the /jobs API endpoints, but retrying of this type of regularly scheduled background job is not supported as we don't want to accidentally create multiple competing scheduled jobs.
• Adds a min_seed_file_crawler_image value to the Helm chart that is checked before creating a crawl from a workflow if set. If a workflow cannot be run, return the detail of the exception in CrawlConfigAddedResponse.errorDetail so that we can display the reason in the frontend

## Todo

- Modify test chart crawler release back to latest once crawler with seed file support is properly released

[tw4l]

Some of the all crawls tests toward the end of the test run in test_uploads.py are periodically returning 502, I'm not quite sure what's happening there but will keep looking into it. Otherwise this is now ready for review.

[SuaYoo]

Reviewing functionality of API changes against frontend-upload-seed-url-list, working well! I didn't review code or other functionality.

[tw4l]

Converted to draft while making sure the cron job to clean up unused seed files is working as expected. Getting close but there seems to be a permissions issue preventing the batch job from being created in the default k8s namespace:

future: <Task finished name='Task-4' coro=<BackgroundJobOps.ensure_cron_cleanup_jobs_exist() done, defined at /app/btrixcloud/background_jobs.py:478> exception=FailToCreateError([ApiException()])>
Traceback (most recent call last):
  File "/app/btrixcloud/background_jobs.py", line 480, in ensure_cron_cleanup_jobs_exist
    await self.crawl_manager.ensure_cleanup_seed_file_cron_job_exists()
  File "/app/btrixcloud/crawlmanager.py", line 257, in ensure_cleanup_seed_file_cron_job_exists
    await self.create_from_yaml(data, namespace=DEFAULT_NAMESPACE)
  File "/app/btrixcloud/k8sapi.py", line 190, in create_from_yaml
    created = await create_from_dict(
              ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/kubernetes_asyncio/utils/create_from_yaml.py", line 148, in create_from_dict
    raise FailToCreateError(api_exceptions)
kubernetes_asyncio.utils.create_from_yaml.FailToCreateError: Error from server (Forbidden): {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"cronjobs.batch is forbidden: User \"system:serviceaccount:default:default\" cannot create resource \"cronjobs\" in API group \"batch\" in the namespace \"default\"","reason":"Forbidden","details":{"group":"batch","kind":"cronjobs"},"code":403}

The job was previously in the crawlers namespace, but that meant it didn't have access to secrets it needed e.g. for database access.

Will continue to work on this tomorrow unless @ikreymer beats me to the punch

Edit: resolved

[tw4l]

@ikreymer Seed file cleanup is now working, tested locally, passing in CI, and more configurable via helm chart values. Ready for your eyes again.