Upgrade Ruby to 3.2.6 & NodeJS to 22

[tpendragon]

Acceptance Criteria

• Ruby is upgraded to 3.2.6
• NodeJS is upgraded to 22

Steps

1. Update .tool-versions and circleci/config.yml to have new versions.
2. Get tests passing.
3. Send Draft PR
4. Adjust group_vars for staging/prod for new versions in princeton_ansible.
5. Provision one staging box.
6. Deploy branch to staging box.
7. Provision all staging boxes.
8. Deploy branch to staging boxes.
9. Make sure everything's working.
10. Provision some production boxes.
11. Deploy to those production boxes.
12. Provision rest of production boxes.
13. Deploy to rest of production boxes.
14. Make sure everything's running.
15. Merge all the PRs.

Notes

If you need or want to remove nodes from the load balancer you can do so with cap --hosts=<host> staging application:remove_from_nginx, and put it back with cap --hosts=<host> staging application:serve_from_nginx

[tpendragon]

Blocked on #182

[hackartisan]

Unblocking this because we haven't had the opportunity to move #182 forward; we can go ahead and finish these upgrades and come back to that later.

[hackartisan]

The PRs were simple and are ready. Ran into some roadblocks deploying / provisioning staging:

• The staging user no longer existed on the aspace-staging machine. Regine helped add it back with the correct access type via the aspace API.
• the new abid-staging box had an IP that lyrasis didn't know about, probably because it was moved to the lib subnet and we never gave them those
• (not yet resolved) aspace client connections work from the staging box in the rails console, but not when executed via nginx/passenger in service of a pageview. Not sure if this is related, but abid seems to think it's running in the production environment even though the RAILS_ENV var is set to staging.