Updates to Dependencies, Build Chain, and Examples

[cmoesel]

This PR makes non-trivial updates to some of our dependencies, our build chain, and our examples. These changes include:

• Switch from ESLint to Oxlint. ESLint has become more complicated and fragile over the years. Currently, it is keeping us from upgrading to TypeScript 7 and it's not clear if/when that will be unblocked (see typescript-eslint#10940). Oxlint is an extremely fast Rust-based linter built by the same team that built Vite. This change allowed us to replace six ESLint-related packages with a single OxLint package. I also removed a couple of TypeScript rules that I didn't think were necessary.
• Upgrade TypeScript 6 to TypeScript 7. With ESLint gone, we are also able to upgrade to TypeScript 7. TypeScript 7 is 10x faster than TypeScript 6 because it uses a brand new compiler written in Go.
• Replace ts-node with tsx. This was required by the switch to TypeScript 7, but since ts-node is no longer maintained, it makes sense to switch anyway.
• Replace browserify with esbuild. Browserify was cool in 2015, but many web packing tools have surpassed it in performance and robustness. It was last updated in 2024 (and the last update before that was 2020). It has also caused npm audit issues in the past due to transitive dependencies.
• Convert examples to full mini-projects. We currently include three simple examples for different technologies: browser, node, and typescript. This PR makes it easier for users to build, run, and adapt them by providing them as small independent node projects.
• Remove checked in cql4browsers.js. Bonnie used to use cql4browsers.js directly, but nobody does that anymore. Now everyone uses their own web packing library (rollup, esbuild, etc) to integrate cql-execution into their web applications. Now the cql4browsers.js file is part of the build process for the browser example and is git-ignored. No more annoying "dang, I forgot to rebuild cql4browsers" moments!
• Stop support for Node 18. Somewhere along the line, Mocha stopped working with Node 18. The production cql-execution code technically still works with Node 18, but our build tools don't. Since Node 18 was EOLed more than a year ago, it probably makes sense just to drop it since we can't unit test with it anymore.

Some of these changes might be considered breaking (particularly dropping Node 18 and dropping cql4browsers), so we should consider if this warrants a major version change. In practice, I doubt this will break any existing implementations, but if we follow semver strictly, we probably should bump it.

Submitter:

• This pull request describes why these changes were made
• Code diff has been done and been reviewed (it does not contain: additional white space, not applicable code changes, debug statements, etc.)
• Tests are included and test edge cases
• Tests have been run locally and pass
• Code coverage has not gone down and all code touched or added is covered.
• Code passes lint and prettier (hint: use npm run test:plus to run tests, lint, and prettier)
• All dependent libraries are appropriately updated or have a corresponding PR related to this change
• [n/a] cql4browsers.js built with npm run build:browserify if source changed.

Reviewer:

Name:

• Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
• The tests appropriately test the new code, including edge cases
• You have tried to break the code

[codecov-commenter]

Codecov Report

❌ Patch coverage is 66.66667% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 88.70%. Comparing base (214a25b) to head (74d23e5).

Files with missing lines	Patch %	Lines
src/elm/type.ts	0.00%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #374      +/-   ##
==========================================
- Coverage   89.57%   88.70%   -0.87%     
==========================================
  Files          55       59       +4     
  Lines        4855     4933      +78     
  Branches     1391     1429      +38     
==========================================
+ Hits         4349     4376      +27     
  Misses        322      322              
- Partials      184      235      +51     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[dehall]

This looks good to me and I'd be ok with merging as-is. But since it has been a couple weeks since this was submitted you may want to bump dependencies one more time just to get the latest.
My only concern is that this is the kind of PR where the things that go wrong are things I wasn't aware of, like how others interact with the library. But to your point, I think if we bump the major version number then anyone who is using this should be able to figure out any breaking changes.

[cmoesel]

@dehall - your comments have been addressed. Based on your comment, I think you are advising we bump a major version, right? (BTW -- I'll also update the GH merge criteria to no longer check cql4browsers once this is ready to merge to master).

[dehall]

@dehall - your comments have been addressed. Based on your comment, I think you are advising we bump a major version, right? (BTW -- I'll also update the GH merge criteria to no longer check cql4browsers once this is ready to merge to master).

I guess to be precise I would say, I think that the next tagged release (whenever that is) should be a bump to the major version. I'm also thinking about my Decimal changes which will impact how users interact with this library, so I'd propose waiting for that before releasing the next version. The fqm-execution team also wants to do a more detailed regression test as well. (And let's also consider if there's anything else we want to try to get in before that. For example I'd kind of like to take a little time to do a quick pass of tightening up types and reducing the use of any)

[hossenlopp]

Just chiming in here since I was able to run a large regression test on this PR vs master with fqm-execution. No changes with results or issues at all. This gets a thumbs up from me. 👍

[cmoesel]

Thank you for the reviews and testing, @dehall and @hossenlopp. Dylan -- holding off a release until the Decimal work (and possibly more breaking changes) sounds like a good plan.