Dependency housekeeping

[MarcAstr0]

Description

Several dependencies have been upgraded, and their versions have been bumped to keep Booster as updated as possible. Some dependency upgrades required a more significant overhaul and will be addressed in upcoming PRs.

Changes

• Update package.json of all packages with the upgraded dependency versions.
• Refactored tests in the CLI package to work with the upgraded oclif.

Checks

• Project Builds
• Project passes tests and checks
• Updated documentation accordingly

[MarcAstr0]

/integration sha=06d78cd7738056d157ba55250f1415439ed7974a

[github-actions]

Oops, looks like you forgot to add a changeset.

⚠️ Please run rush change and commit the changeset file.

This command will prompt you for a change description and generate a changeset file. You can read more about changesets here.

Remember that you should use the version bump that is appropriate for the change you are making:

Version bump	Meaning
patch	Bug fixes, documentation changes, etc.
minor	New features, non-breaking changes
major	Breaking changes

If you are unsure about which version bump to use, please ask in the comments and we will help you out.

[github-actions]

✅ Integration tests have finished successfully!

[davidverdu]

LGTM! I left some comments I wanted to do due to major version upgrades in some packages. Nonetheless, I think the PR is OK because the tests are passing.

[MarcAstr0]

@davidverdu all major-version upgrades were tested and made sure nothing broke. As explained in the PR description, major versions that broke code will have to be addressed separately in another PR.