enhancement: pin exact dependency versions in console

hi, i wanted to open a discussion about pinning exact dependency versions in the console package.json file. right now the dependencies use the caret (^) symbol which allows minor and patch updates when running npm install. while package lock already pins versions for npm ci, developers running npm install might get different versions over time which could introduce subtle differences in behavior or build output. for reproducible builds and consistency across all developer environments i think it would be helpful to remove the caret symbols and pin exact versions like "react": "19.2.4" instead of "react": "^19.2.4". this would make it clear exactly which versions the project uses and prevent any accidental upgrades. i understand this means more manual work when updating dependencies but it gives us full control and transparency. would the maintainers and active contributors [ @jbonofre @binarycat0 @dimas-b ] be open to discussing this change? i am happy to prepare a separate pull request if you think this approach makes sense for the project. thank you for your time.

Start by locating the console package.json and review its dependency version specifiers, especially the React entry mentioned in the issue. Compare the manifest with the existing package lock and consider both npm install and npm ci behavior. Done means the intended console dependencies use exact versions and the resulting dependency state remains consistent.

Written by the indexing model from the issue text.