Feature description

This issue for tracking work on archiving old builds. Archived builds should only keep the lockfile; if they become activated again, the lockfile should be used to reinstall the environment from scratch. Proposed approach:

1. Create an endpoint to archive a build: /api/v1/build/{build_id}/archive/
2. Add a button to conda-store-ui to archive old builds of an environment.

Value and/or benefit

Archiving old builds will save disk space for deployments with many old builds.

Anything else?

No response