Add tk_version token, toolkit formatted version string (+5 squashed commits)
Squashed commits:
[c721df2] added description for version_template required config setting
[20d99b3] cleaner solution for hiero_version template
[bee4fd2] use hiero_version template for formatting version string for tk
[8ca5445] use tk_version for token and format it using a tk version TemplateKey
[0547612] sip nuke script published file creator

added description for version_template required config setting

Comment updates, renamed setting to template_version for consistency. Updated tooltip for {tk_version}
add nuke script and plate as published files
write MetadataNodes for tk-nuke-writenode to convert to TankWrite nodes.
get the published_file_type from the nuke context settings
fix typo
Merge branch 'master' into 22399_published_files

Conflicts:
	python/tk_hiero_export/version_creator.py
Ticket #22399:
- Added nuke_script_path_step to info.yml
- Added plate_published_file_type to info.yml
- Added nuke_script_toolkit_write_nodes to info.yml

Introduced setting to specify the toolkit write nodes to make available to Hiero.
The UI in Hiero gets built independent of the tasks, so all the template paths
to the nuke scripts have no way to be resolved.  Instead of having a dependency
on the shot task environment implied by the export, just be explicit about the
node profiles to use.

Introduce a new GUI element to allow the export to toggle the different nodes
on and off.
Ticket #22399 - Override sequenceName so the resolver gets an answer compatible
with collation.
added nuke_script_published_file_type to info.yml

Instead of trying to infer what the tank_type should be for published Nuke Scripts, allow that to be set explicitly in the app settings.
Merge pull request #2 from shotgunsoftware/22399_published_files

#22399 create published files for plates and nuke script. Add support for setting up tk write nodes in nuke script.