Add status deprecated to the packages statuses

What does this MR do and why?

Introduce the new status deprecated to the packages statuses. It'll be first used by npm packages that become deprecated.

The MR changes the Packages::Npm::DeprecatePackageService to also update the status to deprecated for packages when they are deprecated.

Additionally, GraphQL and REST API endpoints were changed to also return deprecated packages.

Since the deprecation operation was already supported by the Package registry for a while, this MR also adds the background migration to update the status to deprecated for existing deprecated npm packages.

References

Please include cross links to any resources that are relevant to this MR. This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.

• UI: display a badge when the npm package is dep... (#474231 - closed)

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

No.

How to set up and validate locally

1. Publish npm package to GitLab package registry docs.

2. Deprecate the package docs.

3. Verify that the package's status was changed to deprecated.

   ::Packages::Package.find_by(name: <package-name>).status

4. Visit the package's details page http://gdk.test:3000/<project full path>/-/packages/<package-id> and check that it contains the deprecation notice:

   This package version has been deprecated.

5. Undeprecate the deprecated package docs.

6. Verify that the package's status was changed from deprecated to default.

   ::Packages::Package.find_by(name: <package-name>).status

Related to #474231 (closed)