Don't break blocks with swords in creative

[Commandcracker]

Description

You can't break blocks in creative while holding those items.

Testing

tested with those items.

Checklist

Things need to be done before this Pull Request can be merged.

• Code is well-formatted and adheres to project style guidelines: cargo fmt
• Code does not produce any clippy warnings: cargo clippy
• All unit tests pass: cargo test
• I added new unit tests, so other people don't accidentally break my code by changing other parts of the codebase. How?

[DataM0del]

Why not just check if it's a sword instead of having a hardcoded list of items?

[Commandcracker]

is_sword is also hardcoded, and it is missing the trident and mace

[DataM0del]

is_sword is also hardcoded, and it is missing the trident and mace

🤦
something filtering over all items could filter using contains and checking if the item name contains sword

itemName.contains("sword")

Also, doesn't Minecraft have metadata for which category or what type of item this is (e.g. swords)?

[Snowiiii]

This is something we want to have abstractions to work with. I would consider an System simliar to the current Interactive blocks System. In the future we will have to add more logic to items and for example a method like Mojang uses canMine would be great

[OfficialKris]

#350 would also benefit from an "item manager." This seems to be pretty important, especially with the rise in added functionality to individual items. I can start work on it once I finish #388 or someone else can give it a shot. Currently, the handle functions have too much going on. Those function should only find out which item is being used and then run the corresponding category, modifier, and specific item code (pickaxes, enchantments, spawn eggs).