uds publish <ocipath> --version does not completely honor the tag override

[michaelabix]

Environment

App version: v0.18.0

Steps to reproduce

1. Publish a uds bundle to a registry by running uds publish <ociPath> --version 0.0.1-test
2. Check the registry for the new artifact

Expected result

One artifact tagged with the --version override of 0.0.1-test

Actual Result

Two artifacts - one tagged with the version metadata from inside the bundle and one tagged with the version override

Visual Proof (screenshots, videos, text, etc)

Severity/Priority

Additional Context

This is something that deliver and others requested in August, as many of us had been overriding the version by using sed or yq on the uds-bundle.yaml file in pipelines prior to running the uds create command. This prevents us from inadvertently overwriting production releases that have the same version. Technically there's a workaround, but this is very inconvenient.

Tag overrides were originally requested in #888