feat: add support 3dsmax 2027 addons

[ZainAallii]

Fixes:

What was the problem/requirement? (What/Why)

PR #224 added a base 3ds Max 2027 host configuration script, but customers using the common renderer + plugin combinations (V-Ray, Corona, tyFlow, Forest Pack, RailClone, FloorGenerator, MultiTexture) had no ready-to-use scripts for 3ds Max 2027.

What was the solution? (How)

Added four new host configuration scripts under host_configuration_scripts/3dsmax/, each in its own folder with a .ps1 and README.md:

• 3dsmax-2027-and-vray/ — 3ds Max 2027 + V-Ray
• 3dsmax-2027-and-corona-14/ — 3ds Max 2027 + Corona 14 (Corona 14 is the first version to support 3ds Max 2027)
• 3dsmax-2027-and-vray-and-tyflow/ — 3ds Max 2027 + V-Ray + tyFlow
• 3dsmax-2027-vray-and-aec-plugins/ — 3ds Max 2027 + V-Ray + Forest Pack + RailClone + FloorGenerator + MultiTexture

All scripts follow the patterns established in the existing 2025 scripts and the per-installer S3 URI variable convention introduced in #216.

What is the impact of this change?

Customers running 3ds Max 2027 jobs on Deadline Cloud Service Managed Fleets now have ready-to-use host configuration samples covering the most common renderer and plugin combinations. They only need to fill in their S3 URIs and configure their fleet.

How was this change tested?

• Validated PowerShell syntax with the AST parser locally (zero parse errors)
• End-to-end tested the overall install pattern (3ds Max 2027 + V-Ray + Corona + tyFlow + Forest Pack + RailClone) against a Service Managed Fleet worker. All add-ons except V-Ray installed successfully and the verification block passed for everything except V-Ray (turned out to be a wrong installer variant downloaded from Chaos, not a script issue)
• The plugin download bug ("$pluginsDir\" getting mangled by PowerShell quoting) was caught during testing and fixed in this commit using Split-Path -Leaf to derive explicit destination filenames

Was this change documented?

Yes — each new folder includes a README.md with installation steps and the prerequisites for that combination.

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[seant-aws]

I might not have the full context on this, but whats the state of all these different licenses? Is it easy for us to understand licensing for all these separate addons in case there's issues ?