feat(worker): add named template for workpool name and base job template

[cnfrancis]

Summary

Have this use case to be able to deploy the same workpools to different data centers in different regions.
Using argocd at runtime we inject such information which we consume in an internal wrapper chart.
The change introduced in this PR will allow us to redefine the named template in our wrapper chart so that following in argocd will work:

helm template \
 -f values/worker-values.yaml \
 -f values/dev/workers/worker-values.yaml \
 -f values/dev/workers/admin.yaml \
  --set region=amer

From this above in our wrapper chart - will be able to build the workpool name dynamically as well allow dictionary merging of baseJobTemplate

Otherwise we have to duplicate per region e.g

helm template \
 -f values/amer/worker-values.yaml \
 -f values/amer/dev/workers/worker-values.yaml \
 -f values/amer/dev/workers/admin.yaml \

The changes suggested aim to be backward compatible hence why it is wrapped in a named template with the same value reference as before.

Requirements

• Contributing guide has been read
• Title follows the conventional commits format
• Body includes Closes <issue>, if available
• Added/modified configuration includes a descriptive comment for documentation generation
• Unit tests are added/updated
• Deprecation/removal checks are added in templates/NOTES.txt
• Relevant labels are added
• Draft status is used until ready for review

[cnfrancis]

hello @mitchnielsen @desertaxle, hope you're all well!
what are your thoughts on this PR ? and generally speaking what is your release schedule like?

[mitchnielsen]

Thanks for the contribution @cnfrancis! Taking a look now.

We don't have a set release schedule. We usually create a release after merging a PR.

[mitchnielsen]

There's a named template matching this, but not a user-configurable Helm value for it, right? We should be able to remove this block.

[mitchnielsen]

This is looking good overall, just a suggestion on the added Helm value. Could you also please add some unit tests to make sure this is working as expected? You can see examples in charts/prefect-*/tests/.