Troubleshooting ESPv2 Container Deployment and Image Naming Issues

We have followed the ESPv2 App Engine (https://cloud.google.com/endpoints/docs/openapi/set-up-app-engine-standard-environment-espv2) documentation steps to build and deploy new containers and services. The images are stored in the Container Registry.

However, we've noticed that the newly created images have different names than previous ones. The format of the image name is correct according to the documentation as `<ESP_VERSION>-<CLOUD_RUN_HOSTNAME>-<CONFIG_ID>`, but recently the image names have included the prefix `no-new-use-public-image` (as shown in the screenshot below).

Additionally, during the "Deploying the ESPv2 container" step using the `gcloud run deploy` command, we encounter an error indicating that the images cannot be accessed, even though the image url is correctly and the necessary permissions have been granted.

Cloud Run API check failed. Requests will be rejected after January 2025 hard enforcement deadline. User does not have access to image gcr.io/<project_id>/endpoints-runtime-serverless:<image_name>

Why did the image name change like that and is this name change causing an error when deploying the espv2 container on cloud run?