Max: TyCache Family Enhancement

[moonyuet]

Changelog Description

This PR introduces several small enhancements on TyCache Family

1. Code tweaks to support multiple export-particle operators with different names in both TyCache and TySpline Family.

2. Supports the export mode of tyCache Splines (Split tycache families into two, one is tyCache and the other is tySplineCache)

3. Optional Validator for frame range in both TyCache and TySpline Family
   

4. Add Loader with tySplineCache modifiers for tySpline Family

Additional info

Template path naming has changed so please ensure you have the updated settings with updated addons.
Check with the following project settingto see if it has the aligned settings with the screenshot below
Openpype:
project_settings/global/tools/publish/template_name_profiles

AYON:
Make sure your addons are at the right version.
Core: v0.1.5, Max: v0.1.4, Openpype: 3.17.7-nightly.7
And make sure you have the tycache template path set in Anatomy Presets

***This can be ready for review after the adjustment on the representation data.

Testing notes:

1. Launch 3dsMax via launcher
2. Create TyCache/TySpline Family with tyFlow object which has events and export-particle operators with different names
3. Publish
4. Make a new scene
5. Load the cache back

[ynbot]

Task linked: OP-7406 3dsmax: tyCache enhancements

[moonyuet]

Will close the related PR #5901 on removing creating TyCache Object after this PR has been approved.

[mkolar]

@moonyuet we'll need AYON port before merging please

[BigRoy]

Quite a big PR - didn't go through it in too much detail since it's 3DsMax and TyFlow - two things I know close to nothing about. Just commented on stuff that stood out to me on a quick read. Likely best for someone from the Ynput team to go through in more detail instead.

I have a feeling that it's a bit overcomplicated for some reason, but I can't put my finger on it why I feel that way because maybe it's needed for what you're trying to do.

[moonyuet]

Quite a big PR - didn't go through it in too much detail since it's 3DsMax and TyFlow - two things I know close to nothing about. Just commented on stuff that stood out to me on a quick read. Likely best for someone from the Ynput team to go through in more detail instead.

I have a feeling that it's a bit overcomplicated for some reason, but I can't put my finger on it why I feel that way because maybe it's needed for what you're trying to do.

I can see your point.
I can't find the best way to get the multiple operators to be exported due to the limitation of tyflow API (maybe the 3dsmax api limitation too). I hope tyFlow API can eventually improve the API so that I dont need to implement some new stuff which is a bit over-engineered for the host to store the related data.

[dee-ynput]

closing: won't do - implemented in AYON (ynput/ayon-3dsmax#1)