chore(many): Upgrade nx

[dschom]

Because

• Now that we are node 24 we can upgrade
• A new version of NX has been released
• We want to improve caching

This pull request

• Upgrades NX, Next, Jest, and other support deps
• Updates deprecated Jest assertions
• Fixes a couple caching issues
• Sets robust nx defaults that work well with our project
• Removes NX commands from package.json 'scripts'. They are no longer permitted by nx.

Issue that this pull request solves

Closes: FXA-14141

Checklist

Put an x in the boxes that apply

• My commit is GPG signed.
• If applicable, I have modified or added tests which pass locally.
• I have added necessary documentation (if appropriate).
• I have verified that my changes render correctly in RTL (if appropriate).
• I have manually reviewed all AI generated code.

How to review (Optional)

• Key files/areas to focus on:
• Suggested review order:
• Risky or complex parts:

Screenshots (Optional)

Due to improved caching response, we now see faster service startup times, which are particular noticeable in the CI. For example current state (from randomly selected run):

With this PR's changes:

Other information (Optional)

There are some commands that now just have exit 0 in them. This is because dependencies are now managed by NX. This means you need use NX to run certain common commands. You can still run the 'sub' commands with yarn workspace directly.

For example, yarn workspace fxa-settings build is now nx run fxa-settings:build OR yarn workspace fxa-settings:build-ts && yarn workspace fxa-settings build-css.

[vbudhram]

@dschom I tested this locally and it runs fine. There does not seem to be a big increase in start up speed? Just the couple questions otw probably good to merge.

###########################################################
#  ✅ Services ready in 123s (infrastructure was started earlier)
###########################################################

  📍 Verifying started services:
     fxa-content-server   http://localhost:3030  OK
     fxa-profile-server   http://localhost:1111/__heartbeat__  OK
     fxa-auth-server      http://localhost:9000/__heartbeat__  OK
     fxa-settings         http://localhost:3000/settings/static/js/bundle.js  OK
     123done              http://localhost:8080  OK

  All started services responded.
  💡 Run 'yarn ports' to see all service ports
###########################################################

[nshirley]

Leaving a comment here from a slack thread, perhaps this fix can be rolled into this PR:

The Start services for playwright tests step jumped from ~2m to ~6.5m because start-services.sh uses -t build --skip-nx-cache. That flag was added in FXA-14006 after #20688 dropped build from the start target. A plain cache hit left content-server's gitignored app/dist bundle missing, so it hung at boot. To restore fast cached builds we would need to declare app/dist as an nx build output for content-server (it's gitignored + not in the defaults), then drop --skip-nx-cache from the start-services.sh.

But, maybe there's a better way to handle this? The short version is just, content-server fails to boot because of an incomplete cache, forcing a full rebuild of the stack for functional-tests.