Add CreatePackagesNpmMetadataCacheRegistry table

What does this MR do and why?

Part of #408278 (closed)

Adds CreatePackagesNpmMetadataCacheRegistry table to track replication and verification state.

Screenshots or screen recordings

No.

Database migrations ouput

Up

$ rails db:migrate:up:geo VERSION=20230606202610
geo: == [advisory_lock_connection] object_id: 226700, pg_backend_pid: 28043
geo: == 20230606202610 CreatePackagesNpmMetadataCacheRegistry: migrating ===========
geo: -- create_table(:packages_npm_metadata_cache_registry, {:id=>:bigserial, :force=>:cascade})
geo: -- quote_column_name(:verification_failure)
geo:    -> 0.0000s
geo: -- quote_column_name(:last_sync_failure)
geo:    -> 0.0000s
geo:    -> 0.0086s
geo: == 20230606202610 CreatePackagesNpmMetadataCacheRegistry: migrated (0.0091s) ==

geo: == [advisory_lock_connection] object_id: 226700, pg_backend_pid: 28043

Down

$ rails db:migrate:down:geo VERSION=20230606202610
geo: == [advisory_lock_connection] object_id: 226520, pg_backend_pid: 27357
geo: == 20230606202610 CreatePackagesNpmMetadataCacheRegistry: reverting ===========
geo: -- drop_table(:packages_npm_metadata_cache_registry, {:id=>:bigserial, :force=>:cascade})
geo:    -> 0.0019s
geo: == 20230606202610 CreatePackagesNpmMetadataCacheRegistry: reverted (0.0050s) ==

geo: == [advisory_lock_connection] object_id: 226520, pg_backend_pid: 27357

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

Related to #408278 (closed)