fix(sys): tweak NodeLazyRequire logic around too-high-versions errors

[alicewriteswrongs]

This changes the logic that we use in the NodeLazyRequire class to
error out in fewer situations. The changes are:

• the data structure for specifying our version ranges is changed from
  [string, string] ([minVersion, recommendedVersion]) to an object
  with minVersion recommendedVersion required properties and an
  optional maxVersion property.
• in the ensure method on NodeLazyRequire we check if maxVersion
  is defined on a given version range requirement.
  • If so, we check that the installed version is greater than or
    equal to minVersion and less than the major version of
    maxVersion.
  • If not, we just check that minVersion <= installedVersion

This should give us the flexibility to mark certain versions of packages
as incompatible (for instance jest@28) without having to do that for all
packages that we lazy require. This is helpful because for most of them
we just want to set a minimum version and don't have a need for an
enforced maximum version.

Pull request checklist

Please check if your PR fulfills the following requirements:

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)
• Build (npm run build) was run locally and any changes were pushed
• Unit tests (npm test) were run locally and passed
• E2E Tests (npm run test.karma.prod) were run locally and passed
• Prettier (npm run prettier) was run locally and passed

Pull request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

What is the current behavior?

GitHub Issue Number: N/A

In #3346 we added a check that packages that we lazy require for testing and whatnot (basically, jest and a few other things) were between the specified minimum version and the recommended version. This will cause an error at runtime if these requirements are not met.

On further reflection this isn't quite the behavior that we want. We only want to enforce a maximum version right now for Jest, not for the other packages we load in this manner, but the implementation in #3346 doesn't have any granularity to it.

What is the new behavior?

• the data structure for specifying our version ranges is changed from
  [string, string] ([minVersion, recommendedVersion]) to an object
  with minVersion recommendedVersion required properties and an
  optional maxVersion property.
• in the ensure method on NodeLazyRequire we check if maxVersion
  is defined on a given version range requirement.
  • If so, we check that the installed version is greater than or
    equal to minVersion and less than the major version of
    maxVersion.
  • If not, we just check that minVersion <= installedVersion

This should give us the flexibility to mark certain versions of packages
as incompatible (for instance jest@28) without having to do that for all
packages that we lazy require. This is helpful because for most of them
we just want to set a minimum version and don't have a need for an
enforced maximum version.

Does this introduce a breaking change?

• Yes
• No

Testing

Unit testing, I also built and tried this out in a test component repo and confirmed that we get errors for Jest but not for other dependencies like puppeteer.

Other information

[rwaskiewicz]

👍 👍 👍