NODEJS-696: Migrate Travis CI to Github Action

[SiyaoIsHiding]

Migrate existing Travis CI tests, also remove Node.js 16.x and add 24.x. Cuz 16.x is EOF and 24.x is the new LTS.

[Copilot]

Pull request overview

This PR migrates the CI/CD pipeline from Travis CI to GitHub Actions, removes support for the end-of-life Node.js 16.x, and adds support for Node.js 24.x LTS.

Key Changes

• Converted Travis CI configuration to GitHub Actions workflow format
• Updated Node.js version matrix to test against 18.x, 20.x, 22.x, and 24.x (removed 16.x)
• Maintained all existing test jobs including ESLint, TypeScript compilation tests, and unit tests

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
.travis.yml	Removed Travis CI configuration file
.github/workflows/travis-ci.yml	Created new GitHub Actions workflow implementing all Travis CI jobs

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

[nitpick] Using --no-save with npm install in CI is redundant since the package.json won't be committed from the CI environment. Consider removing the --no-save flag for cleaner workflow configuration.

[SiyaoIsHiding]

I just wanted to make it clear that version 4.9 overrides

[Copilot]

[nitpick] The unit-latest-deps job omits cache: 'npm' while all other jobs include it. For consistency and to potentially speed up the workflow by caching global npm packages, consider adding cache: 'npm' here as well, even though package-lock.json is removed afterward.

Suggested change

	node-version: 20.x
	node-version: 20.x
	cache: 'npm'

[SiyaoIsHiding]

Will the next GH Action job pick up the cached latest dependencies instead of the fixed dependencies in the package-lock.json?