Target an LTS version of Node

[cjbarth]

This is a semver-major change that will bring the dependencies up to supported versions and more easily allow migration of tests to supported test frameworks.

[cjbarth]

This will use lts/*, lts/-1 and lts/-2, but will do so via [14, 16, 18], which allows us to update package.json's engine as we move forward. This also tests latest, so we make sure that we see any coming issues as node is upgraded.

[parallels999]

Hi, when will there be a new release with these changes?

[cjbarth]

As soon as we finish the TS conversion... which is dependent on goto100/xpath#116 landing. We're getting close. FWIW, this release is holding up the v5 release of passport-saml and node-saml, so there is strong motivation to get this along.

[parallels999]

@cjbarth so, is possible #333 Bump @xmldom/xmldom to 0.8.8 for V3?

Example node-saml:
https://github.com/node-saml/node-saml/blob/9657c6663a44d856684ac96beb5b887c1a2311f6/package.json#L62
https://github.com/node-saml/node-saml/blob/9657c6663a44d856684ac96beb5b887c1a2311f6/package.json#L64
node-saml requires "xml-crypto": "^3.1.0", "@xmldom/xmldom": "^0.8.8"
but xml-crypto v3.1.0 requires "@xmldom/xmldom": "0.8.7"

[cjbarth]

Sure, just make a PR against master, we'll land it, and then make the same thing against 3.x.

[parallels999]

that's the point, master already has this change, ON THIS PR, this is missing in 3.x

xml-crypto/package.json

Line 38 in 131bcf9

"@xmldom/xmldom": "^0.8.8",