fix: bump non-breaking dependencies to latest

[aversini]

PR Type

enhancement, dependencies

---

Description

• Updated multiple dependencies across client, server, and types packages to their latest non-breaking versions.
• Updated the pnpm package manager version in the root package.json.
• Ensured compatibility and stability by keeping dependencies up-to-date.

---

Changes walkthrough 📝

	Relevant files
Dependencies	package.json Update client package dependencies to latest versions        packages/client/package.json Updated @rsbuild dependencies to version 1.0.1-beta.16. Updated @testing-library/jest-dom to version 6.5.0. Updated several development dependencies to their latest versions. +11/-11  package.json Update server package dependencies to latest versions        packages/server/package.json Updated @swc/core to version 1.7.18. Updated husky and lint-staged to their latest versions. +3/-3      package.json Update package manager version in root package.json            package.json Updated pnpm package manager to version 9.8.0. +1/-1      package.json Update types package dependencies to latest versions          packages/types/package.json Updated @types/node to version 22.5.0. Updated @types/react to version 18.3.4. +2/-2
Additional files (token-limit)	pnpm-lock.yaml ...                                                                                                            pnpm-lock.yaml ... +614/-893

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[qodo-merge-pro]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Key issues to review Dependency Update Multiple dependencies have been updated to their latest versions. Ensure that these updates don't introduce any breaking changes or compatibility issues. Dependency Update Several dependencies have been updated. Verify that these updates are compatible with the existing codebase and don't introduce any unexpected behavior. Type Definitions Update Type definitions for Node.js and React have been updated. Ensure that these updates don't cause any type-related issues in the existing codebase. Package Manager Update The pnpm package manager version has been updated. Verify that this update doesn't affect the project's build or dependency resolution process.

[qodo-merge-pro]

PR Code Suggestions ✨

Category	Suggestion	Score
Best practice	Use version ranges for dependencies to allow for minor or patch updates Consider using a caret (^) or tilde (~) version range for the @rsbuild dependencies to allow for minor or patch updates respectively, which can include bug fixes and non-breaking improvements. packages/client/package.json [15-17] -"@rsbuild/core": "1.0.1-beta.16", -"@rsbuild/plugin-react": "1.0.1-beta.16", -"@rsbuild/plugin-type-check": "1.0.1-beta.16", +"@rsbuild/core": "^1.0.1-beta.16", +"@rsbuild/plugin-react": "^1.0.1-beta.16", +"@rsbuild/plugin-type-check": "^1.0.1-beta.16", Apply this suggestion Suggestion importance[1-10]: 8 Why: Using version ranges for dependencies is a best practice that allows for automatic minor or patch updates, which can include important bug fixes and improvements without breaking changes.	8
	Use a version range to allow for minor updates of a dependency Consider using a caret (^) version range for the @swc/core dependency to allow for minor updates, which can include performance improvements and bug fixes. packages/server/package.json [17] -"@swc/core": "1.7.18", +"@swc/core": "^1.7.18", Apply this suggestion Suggestion importance[1-10]: 8 Why: Allowing minor updates for dependencies like @swc/core can provide performance improvements and bug fixes, enhancing the stability and efficiency of the project.	8
	Use version ranges for type definition packages to allow for minor updates Consider using a caret (^) version range for the @types/node and @types/react dependencies to allow for minor updates, which can include new type definitions for newer Node.js and React versions. packages/types/package.json [21-23] -"@types/node": "22.5.0", -"@types/react": "18.3.4", +"@types/node": "^22.5.0", +"@types/react": "^18.3.4", Apply this suggestion Suggestion importance[1-10]: 8 Why: Using version ranges for type definition packages ensures compatibility with newer versions of Node.js and React, providing updated type definitions and reducing maintenance overhead.	8
Maintainability	Simplify the packageManager field by removing the SHA hash Consider removing the SHA hash from the packageManager field, as it's not typically necessary and can make the package.json file harder to read and maintain. package.json [7] -"packageManager": "[email protected]+sha512.8e4c3550fb500e808dbc30bb0ce4dd1eb614e30b1c55245f211591ec2cdf9c611cabd34e1364b42f564bd54b3945ed0f49d61d1bbf2ec9bd74b866fcdc723276" +"packageManager": "[email protected]" Apply this suggestion Suggestion importance[1-10]: 7 Why: Removing the SHA hash from the packageManager field simplifies the package.json file, making it easier to read and maintain without affecting functionality.	7