add project status marker

[dgonzdev]

issue: #4678

this pr adds a status marker field to the rubygem db table and api response following the patterns laid out in python's proposals:

• https://peps.python.org/pep-0792/
• https://blog.pypi.org/posts/2025-01-30-archival/
• https://blog.pypi.org/posts/2024-12-30-quarantine/
• Allow project owners to set status markers ("deprecated", "archived", etc) to their PyPI projects pypi/warehouse#16844

at a high level, the proposal is to have a status marker that is "

• machine-readable,
• general (i.e. conveys more than one possible state), [that] applies to the entire project,
• instead of per-release or per-distribution
  "

the status marker can be leveraged to implement an archival feature, temporarily quarantining gems with suspected security issues, and more.

couple of questions to consider

• should the field in the api be called status?
• should we return "active" in the api when the status_marker in the db is null?

the follow up work would be to

• implement the ui to mark the gem as archived
• decide the rules/tools for quarantining a gem
• decide what other behavior can be built on top of this status/build it