[CI] Build and consume source wheel artifacts across Jenkins platforms

[tqchen]

Build pinned-source FFI, TIRx and TVM wheels in Jenkins and transfer the three packages through dist/. A single build-dependency script prepares writable backend and Z3 prerequisites in .local/python; Groovy calls the root platform build script and prints cache statistics.

Root platform scripts own the complete platform options and three direct wheel builds in FFI, TIRx, TVM order. All three use the same root CMake source/build tree, native settings and source version; fixed tvm_ffi, tvm_tirx and tvm install components select each package's payload. Run enabled C++ tests from that shared native tree. Retain standalone TIRx platform scripts for future independent use; Wasm orchestration remains in parent TVM.

Source the small wheel-installation script before test commands in Groovy. It installs the three package-prefix globs offline without dependency resolution into .local/python, keeps the pinned ORCJIT prerequisite, and exports installed-package paths and source resources. Python, docs, Java and Wasm entrypoints use that caller-provided environment. Java discovers native artifacts through package configuration, and relative library paths keep the separate packages relocatable.

Use image compiler wrappers, IAM-role S3 caching, existing parallel bounds and Docker environment forwarding. Preserve Jenkins retry behavior and optional GPU shared-library packaging. Resolve OpenCL headers through the configured SDK or pinned CMake FetchContent when OpenCL is enabled, replacing the header submodule. Build macOS and Windows parent wheels against the explicitly installed local TIRx artifact. Remove redundant CI/build wrappers and document direct development commands.