Document archiving and unarchiving a project

[jeremy]

You can archive and unarchive a project over the API. Both endpoints already existed, but they were undocumented and answered JSON requests with a redirect instead of a status code. They now return 204 No Content, and they're documented.

Archive a project — PUT /projects/1/status/archived.json

Unarchive a project — PUT /projects/1/status/active.json, which restores a project from the trash as well as from the archive.

This closes a gap in the docs: GET /projects.json?status=archived has always let you read archived projects, but there was no documented way to set that status.

Two responses worth knowing about, both documented:

• On accounts where archiving and trashing projects is limited to admins and the project's creator, everyone else gets a 403 Forbidden when archiving. Unarchiving is not restricted this way.
• Unarchiving returns 507 Insufficient Storage when the account has reached its project limit, with the same error body already documented under "Create a project".

If you're already calling these endpoints, they used to return a 302 to a URL that then failed. You'll now get a 204 directly. The archive or unarchive itself succeeded in both cases — the difference is that there's no longer a redirect to follow.

---

Synced from bc3 doc/api/ by script/api/sync_to_bc3_api — not a hand-edit.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.