build: Update to lerna 7.x

[mofojed]

• Removed useWorkspaces flag (no longer used)
• Add provenance flag to .npmrc
• Fixes Add provenance to published npm packages #1235
• Tested npm start, npm test, and npm run build steps and ensured they all worked correctly

[codecov]

Codecov Report

Merging #1417 (22ad468) into main (7480280) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1417   +/-   ##
=======================================
  Coverage   45.71%   45.71%           
=======================================
  Files         511      511           
  Lines       35065    35065           
  Branches     8767     8767           
=======================================
  Hits        16029    16029           
  Misses      18985    18985           
  Partials       51       51           

Flag	Coverage Δ
unit	45.71% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

[mattrunyon]

Have you tried publishing an alpha version from this branch? Should probably do that to ensure the provenance stuff works

[mattrunyon]

There is also an issue w/ caching and build. I ran a build, changed vite.config.ts, then ran build again and it used the cached build. Probably something I didn't get right when I tried setting up nx the first time.

And another issue w/ nx is it causes .env files to load differently and doesn't play nicely with Vite. npm start doesn't load .env.development b/c nx loads .env first, so Vite does not override previously set env variables. The LogProxy is on in dev mode (should be off) and the base URL is relative and not /ide/ like .env.development specifies

See #1011 (comment) for previous issues

[mofojed]

I'll just add back the useNx: false flag - that wasn't the point of this change anyways, leave debugging that issue to another time. Good catch though!

[mattrunyon]

Need to add provenance=true to .nvmrc or "publishConfig": { "provenance": true } to package.json to enable it

[mattrunyon]

Looks like the action change will need to merge before we can validate this publishes properly, but looks like it should based on the failed publish saying it needs the id-token permission