LabVIEW CI 4.18.0

Adds a release-driven GitLab distribution mirror so GitLab projects can bootstrap the same canonical LabVIEW CI implementation without a second codebase. GitLab-source installs record their archive origin in the manifest, and later bootstrap updates re-fetch that origin instead of relying on a stale local installer; immutable release tags remain protected while channel aliases advance with the mirror. Added an installable native GitLab CI provider for custom workers, Mass Compile, VI Analyzer, Unit Tests, Antidoc, SBOM Generation, Builds, VIDiff, and both snapshot paths. It publishes private project-registry workers, preserves Pages report history, and keeps existing root GitLab pipelines safe during installation. GitLab-hosted Linux Docker-in-Docker worker builds are verified; Windows jobs still need a self-managed Docker-capable runner. Linux VIPM bakes now show install phases and fail closed with focused diagnostics when a package action fails, so incomplete workers are never published. A package-owned post-install VI must itself support unattended Linux execution; VIPM cannot safely skip it.

Consumers pinned at the major alias (e.g. @v4) receive this automatically.