chore: support adaptor wheel overrides on Windows and Linux

[karthikbekalp]

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

The Include Adaptor Wheels developer option used a Linux-specific Bash setup action and hard-coded worker paths, so locally built adaptor wheels could not be exercised reliably on Windows workers.

What was the solution? (How)

• Replace the Bash override action with an embedded cross-platform Python setup script.
• Create a worker virtual environment with the active queue Python, install the three attached wheels without replacing queue dependencies, and propagate the virtual environment through OpenJD environment changes.
• Validate the installed adaptor executable and emit its attached package version in an ADAPTOR_OVERRIDE_READY diagnostic marker.
• Correct wheel-directory and normalized Cinema 4D wheel-name validation.
• Add focused tests for Windows and Linux paths, wheel selection, environment changes, and package-version reporting.

What is the impact of this change?

The developer-only Include Adaptor Wheels workflow now works on Windows and Linux workers. Normal submissions that do not enable the option are unchanged.

How was this change tested?

• hatch run fmt
• hatch run lint
• hatch run all.py3.11:lint (reproduces the previously failing CI environment)
• hatch run test (380 passed, 6 skipped)

Both live jobs in Windows and Linux loaded the exact attached Cinema 4D adaptor wheel, emitted ADAPTOR_OVERRIDE_READY, and completed cinema4d-openjd --help successfully.

Was this change documented?

No documentation change is required for this developer-only option.

Is this a breaking change?

No.

---

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