Fix tags #68

[Giovanniricotta2002]

This pull request introduces several improvements to the development workflow and item tagging conventions, focusing on better integration with Forge tags, more organized item categorization, and enhanced VSCode support for running and building the project. The changes streamline how items are tagged and referenced in recipes, and add configuration files for easier development and testing.

Development Environment Improvements:

• Added .vscode/launch.json with multiple Java launch configurations for running the client, data generator, game test server, and server, each with appropriate VM arguments, environment variables, and pre-launch Gradle tasks for streamlined development and testing.
• Added .vscode/tasks.json defining Gradle-based shell tasks to prepare the environment for each launch configuration, improving build automation and consistency.

Item Tagging and Recipe Consistency:

• Updated item tags in CNItems.java to use more precise Forge conventions (e.g., dusts/uranium, dusts/coal, armors/helmets, etc.), improving compatibility and organization of item categories. [1] [2] [3] [4] [5] [6]
• Updated CNMixingRecipeGen.java to use the new item tags in recipe requirements, ensuring recipes reference the correct, standardized tags.

Code Quality:

• Removed the unnecessary "unused" suppression from the @SuppressWarnings annotation in CNItems.java, improving code clarity.

Bug Fixes:

• Fixed a mixin injection point in BaseFireBlockMixin.java to reference the correct method name (getState instead of an obfuscated name), improving maintainability and compatibility.