feat(repo): upgrade to latest lerna v8 and pnpm v9

[benpsnyder]

I've been using Nx for 5+ years and was excited to see them take over stewardship of Lerna. We should take advantage of the latest updates ... upgrading to latest Lerna and PNPM is easy and will add great performance and value to the project.

This is also done in #413 but I wanted to open a standalone PR for it.

[vercel]

@benpsnyder is attempting to deploy a commit to the Bigcapital Team on Vercel.

A member of the Team first needs to authorize it.

[abouolia]

Perfect, just pushed a commit just to make sure pnpm-lock.yaml is up-to-date.

[abouolia]

@all-contributors please add @benpsnyder for code.

[allcontributors]

@abouolia

I've put up a pull request to add @benpsnyder! 🎉

[benpsnyder]

Perfect, just pushed a commit just to make sure pnpm-lock.yaml is up-to-date.

@abouolia I believe what you did was revert from lockfileVersion: '9.0' to lockfileVersion: '6.0' because you're using an older version of PNPM than latest.

There wasn't a perfect way to enforce the latest PNPM version in the repo so I didn't add that to the PR.

[benpsnyder]

Perfect, just pushed a commit just to make sure pnpm-lock.yaml is up-to-date.

@abouolia I believe what you did was revert from lockfileVersion: '9.0' to lockfileVersion: '6.0' because you're using an older version of PNPM than latest.

There wasn't a perfect way to enforce the latest PNPM version in the repo so I didn't add that to the PR.

I addressed this on my other PRs with the following in package.json

"engineStrict": true,
"engines": {
    "node": "16.x || 17.x || 18.x || 20.x",
    "pnpm": ">=9"
},

[abouolia]

@benpsnyder I have fixed it, thanks for mentioning that.