Remove 'Rolling Tag' logic for Prereleases

[CodeGat]

We are removing the rolling tag logic because it is causing spack installs to fail. This is because when updating the repository in spack, it fails to git fetch --tags because it would clobber the existing tags.
Removes functionality introduced in the CI (back when it was a part of the model) in ACCESS-NRI/ACCESS-OM2#47

In this PR:

• ci.yml: Removed shifting tag logic for prereleases, now only do it initially.

References #85

[aidanheerdegen]

LGTM assuming we still tag again on merge.

[CodeGat]

Indeed we do. That is handled in cd.yml, specifically here:

build-cd/.github/workflows/cd.yml

Lines 25 to 47 in 06ed17b

	push-tag:
	name: Tag Deployment
	runs-on: ubuntu-latest
	permissions:
	contents: write
	outputs:
	name: ${{ steps.tag.outputs.name }}
	steps:
	- uses: actions/checkout@v4
	- name: Generate Tag
	id: tag
	# Get the tag name from the `spack.yaml` that was merged into main, which
	# is of the form `<model>@git.<version>`.
	run: echo "name=$(yq '${{ env.SPACK_YAML_MODEL_YQ }} | split("@git.") | .[1]' spack.yaml)" >> $GITHUB_OUTPUT
	- name: Push Tag
	# NOTE: Regarding the config user.name/user.email, see https://github.com/actions/checkout/pull/1184
	run: |
	git config user.name ${{ vars.GH_ACTIONS_BOT_GIT_USER_NAME }}
	git config user.email ${{ vars.GH_ACTIONS_BOT_GIT_USER_EMAIL }}
	git tag ${{ steps.tag.outputs.name }} --force
	git push --tags --force

:)