Simple knife repath, removes a layer of unecessary nesting

[Tsar-Salat]

Ports:

• Repaths knives to not all be children of the kitchen knife. tgstation/tgstation#62035

About The Pull Request

Repaths all knives from obj/item/kitchen/knife to obj/item/knife, genericized knife behavior is now stored on the parent knife, which shouldnt be spawned in and only be used in checks. Children knives are written like obj/item/knife/rainbow or obj/item/knife/combat

There should be no ingame changes, other than I replaced a single Soviet kit to use a combat knife instead of a kitchen knife.

Why It's Good For The Game

Kitchen knives were the first implemented knives in the game many years ago, and so thus all knives derive from it and use its path as a parent. This works fine, but it can be somewhat confusing in coding or trying to debug why heretic blades or rainbow knives are considered a 'kitchen' tool.

Testing Photographs and Procedure

Screenshots&Videos

All typical knife behavior

dreamseeker_81dZQEhkFp.mp4

Changelog

🆑 rkz, itseasytosee
code: repathed knives, removing unecessary nesting
/:cl:

[PowerfulBacon]

Update the UpdatePaths/scripts to include the repathed items so that in the case of merge conflicts, we can just run the script and resolve them

[PowerfulBacon]

[PowerfulBacon]

Should this have the / at the end?

[Tsar-Salat]

Yes. Those are every knife besides kitchen knives.

/obj/item/kitchen/knife is a kitchen knife. Before it was the parent of all knives, but now it is a derivative of /obj/item/knife. This differentiation is important so regular kitchen knives are converted

In the unlikely event a merge conflict occurs, I will fix it within the hour.