Update the workflow

[HellAholic]

Make the workflow ticket aware across different repositories (including the GcodeAnalyzer)
Moving the script to execute the analyzer to its own repository (to do item) to keep all the connected elements in one place for the analyzer
Using the cura.jinja profile for the build to include the overrides

• Package override action, checks for existing tag before appending it. Required to be fixed to prevent a duplicated tag error Ultimaker/cura-workflows@038066f
• cura.jinja, move the override section to the bottom of the file so we can just append the overrides when required without needing to add the override tag Ultimaker/conan-config@64a4beb

CURA-13110

[github-actions]

Test Results

31 tests  ±0   30 ✅ ±0   5s ⏱️ -1s
 1 suites ±0    0 💤 ±0 
 1 files   ±0    1 ❌ ±0 

For more details on these failures, see this check.

Results for commit 9ec08e4. ± Comparison against base commit 212a4be.

[wawanbreton]

Looks good overall, some suggestion and questions

[wawanbreton]

For more consistency and future-proofness, would it make sense to use the conan-recipe-version action instead ? Since this is the one that generates the conan packages channels, it should always give the proper result even if it iself changes.
This method is simple and much faster though, so this is merely a suggestion.

[HellAholic]

I agree, either we would consume the output of the action or run the action (at least that is my ultimate vision). But for now went with the faster option. So follow up ticket once things are working could be a nice addition.