Fix recommended security vulnerabilities and upgrade lerna to v8.2.2

[Patel-Raj]

Upgraded lerna to v8.2.2 and followed the changelog to fix breaking changes if any for both v7.0.0 and v8.0.0. Ran npx lerna repair as suggested in changelog.

Ran npm audit fix to fix the recommended security vulnerabilities from semgrep

1. node_modules/word-wrap
2. node_modules/ejs
3. node_modules/micromatch
4. node_modules/@octokit/request-error

Fixed test.yml workflow to use actions/setup-node@v4 and actions/checkout@v4 actions and default to Node 18 while running the tests and only execute on pull requests, merge to master and manually trigger.

Output:
run npm fund for details
found 0 vulnerabilities

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	lerna@​6.6.1 ⏵ 8.2.2			+1	+1

View full report

[pdp2121]

LGTM

[mvadari]

FYI be careful with lerna upgrades - one lerna upgrade on xrpl.js made us unable to publish new versions

[Patel-Raj11]

FYI be careful with lerna upgrades - one lerna upgrade on xrpl.js made us unable to publish new versions

@mvadari I was thinking of testing the lerna version update change by releasing @xrplf/eslint-config and @xrplf/prettier-config from my fork to my private npm registry. Do you have any better suggestion to test this?

[mvadari]

@Patel-Raj11 that's probably the best way. Glad you're testing - the last time we tried major-upgrading Lerna (from 4.x to 6.x on the JS repos IIRC) we weren't able to release later 😬

[Patel-Raj11]

@mvadari I tested releasing packages using lerna v8 here. It worked fine. Added capability to independently version and release sub packages in 3084bf6.