Changed namespace, but version tags still appear in original namespace

I published the first several versions of our devcontainer feature without setting `features-namespace` or `templates-namespace`, so they appeared at a default location based on the name of the repository:
https://github.com/tailscale/codespace/pkgs/container/codespace%2Ftailscale

I've since [updated our workflow](https://github.com/tailscale/codespace/blob/main/.github/workflows/release.yaml) to set the namespaces, but new version tags still only appear at the original location.

For example I ran the `devcontainers/action` workflow for 1.0.3 after updating `features-namespace` and `templates-namespace`, but the 1.0.3 tag only appears in the old package location:
https://github.com/tailscale/codespace/pkgs/container/codespace%2Ftailscale

The new location, the one that I actually want to publish to, only gets the `latest` tag.
https://github.com/tailscale/codespace/pkgs/container/codespace

Therefore the prior versions drop out of its view when a new one it published, and it isn't possible for people to reference the devcontainer feature by a specific version.

What I'd like to accomplish is:
- stop adding new versions in https://github.com/tailscale/codespace/pkgs/container/codespace%2Ftailscale, but leave it in place so as not to break people who are already referencing it
- new versions appear only in https://github.com/tailscale/codespace/pkgs/container/codespace, with their tags

Is there a way to accomplish this?

References: https://github.com/devcontainers/devcontainers.github.io/pull/127