refactor: new template version workflow

[asdolo]

What does this do?

Remove New GitHub Release (new-github-release.yml) workflow and replace it with an extra step in the New Template Version (new-template-version.yml) workflow.

Why did you do this?

• To simplify the amount of actions & workflows we have in the repository: The New GitHub Release workflow was only triggered automatically when a new tag is created. There isn't a way to trigger it manually, but even so it was being show in the Actions page.
• Because the two workflows had a similar name and they may be mistaken with each other. Actually, the New Template Version workflow is the one we can manually trigger, and it WILL create a new GitHub version if it doesn't fail.
• Because the New GitHub Release workflow was automatically triggered after new-template-version.yml workflow runs successfully. The behaviour is the same after this refactor.

Who/what does this impact?

N/A

How did you test this?

WIP

[github-actions]

💯 Test Coverage

Lines	Statements	Branches	Functions
	50% (250/500)	41.59% (94/226)	35.93% (69/192)

😎 Tests Results

Tests	Skipped	Failures	Errors	Time
62	0 💤	0 ❌	0 🔥	27.176s ⏱️

👀 Tests Details • (51%)

File	% Stmts	% Branch	% Funcs	% Lines	Uncovered Line #s
All files	50	41.59	35.93	51.04

report-only-changed-files is enabled. No files were changed in this commit :)