chore(smoke-test): Arm "test installers" GHA workflow

[kraenhansen]

Here's a link for a successful run of the workflow: https://github.com/mongodb-js/compass/actions/runs/13292993666

Description

Merging this PR will:

Add the e2e-tests as a dependency of smoke-tests

72b40f2 adds the e2e-tests as a dependency of the smoke-tests package

compass/packages/compass-smoke-tests/package.json

Line 37 in 42d8eb8

"compass-e2e-tests": "^1.29.0",

I'm doing this to leverage Lerna to run "bootstrap" only for the packages that we actually need to run the test:

compass/.github/workflows/test-installers.yml

Lines 142 to 145 in 42d8eb8

	- name: Install dependencies and build packages
	run: npm ci
	- name: Bootstrap packages
	run: npx lerna run bootstrap --scope @mongodb-js/compass-smoke-tests --include-dependencies

Arm the "test installers" workflow

Running the smoke tests (time-to-first-query, auto-update-from and auto-update-to) with various package formats, platforms (MacOS x86 + arm64, Ubuntu Linux x86 and Windows x86) and variants / distributions (regular, read-only and isolated).

For now, I'm disabling a few of these combinations to get a successful run that I can extend to trigger from Evergreen (or some other event) in a future PR:

compass/.github/workflows/test-installers.yml

Lines 92 to 124 in 42d8eb8

	exclude:
	# TODO: See https://github.com/mongodb-js/compass/actions/runs/13281152689/job/37079620322
	- package: osx_dmg
	test: auto-update-from
	# TODO: See https://github.com/mongodb-js/compass/actions/runs/13281152689/job/37079621700
	- package: windows_setup
	test: auto-update-from
	# Skip auto-update tests for isolated and readonly distributions for now
	# This is not supported by the update server we're using in the test harness
	- hadron-distribution: compass-isolated
	test: auto-update-from
	- hadron-distribution: compass-isolated
	test: auto-update-to
	- hadron-distribution: compass-readonly
	test: auto-update-from
	- hadron-distribution: compass-readonly
	test: auto-update-to
	# Temporary skip failing auto-update-to tests
	- test: auto-update-to
	package: osx_dmg
	- test: auto-update-to
	package: windows_zip
	- test: auto-update-to
	package: windows_msi
	- test: auto-update-to
	package: windows_setup
	- test: auto-update-to
	package: linux_deb
	# Skip time-to-first-query tests for readonly because it doesn't have editable documents
	# See https://github.com/mongodb-js/compass/actions/runs/13286945911/job/37097791601
	- hadron-distribution: compass-readonly
	test: time-to-first-query

Refactor the auto-update-to tests

The is introducerd in refactors the auto-update-to tests. The main issue was that the installer for the "subject" of the test was being used to install the existing "latest" package. This was an issue for example on MacOS where we use a "latest" .dmg to test the "subject" .zip release. I didn't notice this before adding assertions on the kind passed to the installer.

Running cleanup on exit, warning on failures

If for some reason some process is keeping files alive in a sandbox directory, Windows was failing the test job even when the actual test succeeded.

5d1188a introduce a warning instead of throwing, as we consider the disks on CI ephemeral anyway. It also registers a listener on the process exiting or getting interrupted to run the clean-up, to make it more gentle on outstanding async work and interruptions while running.

Waiting for auto-update server to close

I had a small suspicion that there that not awaiting the shutdown of the auto-updater server was causing a race condition, but I don't think that's the case. I left in the code to await it closing anyway, in 42d8eb8

Checklist

• New tests and/or benchmarks are included
• Documentation is changed or added
• I have signed the MongoDB Contributor License Agreement (https://www.mongodb.com/legal/contributor-agreement)

Motivation and Context

• Bugfix
• New feature
• Dependency update
• Misc

Open Questions

Dependents

Types of changes

• Backport Needed
• Patch (non-breaking change which fixes an issue)
• Minor (non-breaking change which adds functionality)
• Major (fix or feature that would cause existing functionality to change)