feat: add V-Ray export workflow with tile rendering

[ZainAallii]

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

3ds Max users with V-Ray needed the ability to export .vrscene files and render them using V-Ray Standalone on Deadline Cloud, with support for tile-based region rendering to handle high-resolution outputs. The existing submitter only supported direct 3ds Max rendering through the adaptor.

What was the solution? (How)

Added a V-Ray Standalone export workflow with two modes:

• Local export: Export .vrscene on the workstation, then render on the farm
• Farm export: Export and render entirely on the farm using 3dsmaxcmd + V-Ray Standalone

Tile rendering splits frames into an N×M grid using V-Ray's -region flag, renders each tile as a separate task, then merges them using additive compositing (Pillow for PNG/TIFF/JPG, OpenEXR+numpy for EXR). A V-Ray Export tab is injected into the existing submitter when V-Ray is the active renderer.

Key files: submitter logic, job template generation with embedded render/merge scripts, UI tab, settings dataclass, workflow registry, executable path discovery, and OS-agnostic path mapping.

What is the impact of this change?

• Adds a new V-Ray Standalone submission workflow (no changes to existing 3ds Max adaptor workflow)
• Modifies submit_dialog.py to inject V-Ray Export tab (only when V-Ray is detected)
• Adds one constant to data_const.py
• No changes to adaptor code

How was this change tested?

• 52 new unit tests covering tile coordinate calculation, frame range parsing, output format validation, and vrscene filename generation (all passing)
• Full test suite: 258 passed, 0 failed
• Lint (ruff) and format (black) checks passing
• Manual end-to-end testing: local export + render, farm export + render, tile rendering with merge, on Deadline Cloud farm with 3ds Max 2025 + V-Ray 6

Was this change documented?

Yes. Architecture doc at docs/design/vray-standalone-file-map.md and design specs under .kiro/specs/.

Did you modify schema files?

• Yes
• No

Is this a breaking change?

No. This is a new feature with no changes to existing workflows or APIs.

---

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

test-results.txt
fmt-results.txt
lint-results.txt

[sonarqubecloud]

Quality Gate passed

Issues
10 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
1.2% Duplication on New Code

See analysis details on SonarQube Cloud

[seant-aws]

Looks good, thanks for the followup issues. This is some good stuff !