Rollout REGISTRY_FF_ENFORCE_LOCKFILES on gitlab.com

Context

Preventing a filesystem metadata registry from ... (#1335 - closed) introduced the feature flag REGISTRY_FF_ENFORCE_LOCKFILES which prevents the registry from starting if any of the lock files exists database-in-use and filesystem-in-use and the wrong configuration is used.

Rollout

We should enable the FF in our environments for gitlab.com to ensure the registry can start. We expect the file database-in-use to exists in our bucket, so disabling the database in the config file would make the registry not start properly.

• pre
• gstg
• gprd-cny
• gprd