feat: upgrade to React 19 + modernize TypeScript config, tooling

[JakubAndrysek]

This pull request introduces several improvements to the project, including configuration updates, TypeScript enhancements, and modernisation of the codebase. The changes aim to improve code quality, maintainability, and developer experience.

Configuration Updates:

• Added a .prettierignore file to exclude directories like dist/, node_modules/, and temporary files from Prettier formatting.
• Introduced a .prettierrc configuration file with formatting rules, such as enabling semicolons and setting a print width of 80 characters.
• Updated .vscode/settings.json to enable Prettier as the default formatter, format on save, and exclude unnecessary files from search and file explorer.
• Added a new eslint.config.js file with configurations for TypeScript, React, and React Hooks, including rules and plugins for improved linting.

TypeScript Enhancements:

• Updated src/BlocklyWorkspaceProps.ts to add explicit _ prefixes to unused parameters and refined RefObject types for better type safety.
• Added explicit TypeScript types to useRef, callbacks, and other parts of the code in src/BlocklyWorkspace.tsx and src/dev-index.tsx. [1] [2]

Code Modernisation:

• Replaced ReactDOM.render with createRoot from react-dom/client to align with React 18+ best practices.
• Refactored the JSON structure in src/initContent/content.tsx for better readability and maintainability.

Dependency and Script Updates:

• Updated package.json to include new scripts for cleaning, building, and formatting, as well as updated dependencies for React 19, TypeScript 5, and other tools.

Minor Fixes:

• Removed unnecessary ESLint comments and adjusted code style in multiple files for consistency. [1] [2]

[JakubAndrysek]

Thanks for your work on this project!
I need a working version, so I have forked your react-blockly repo and published a temporary version under my npm account.
If anyone wants to use it, it is published as @kuband/react-blockly.
I will be happy if you merge the PR, and I can move back to using the original package.

[nbudin]

Hi @JakubAndrysek, thanks for doing this! I'm actually looking for new maintainers for this package. Would you be interested in potentially taking over maintainership?

[JakubAndrysek]

Hi @nbudin, thanks for reaching out! I am currently working on my bachelor's thesis which is using this package extensively.
I am currently maintaining also other projects, so I know how much work it can be. However, since I will need to use this package for some time, I can take over the maintainership.
How would you like to proceed?

[nbudin]

Hi @nbudin, thanks for reaching out! I am currently working on my bachelor's thesis which is using this package extensively. I am currently maintaining also other projects, so I know how much work it can be. However, since I will need to use this package for some time, I can take over the maintainership. How would you like to proceed?

Thank you so much! If you could send me an email at natbudin@gmail.com with your contact information, I can go ahead and give you commit access to this repository as well as rights to publish the package to npm. I really appreciate your willingness to take it on!