Add horizontal mouse wheel support

[andrikpowell]

This was slightly more difficult than it should've been. Code is adapted from Woof, and so it works the same way.

Required a delay event only for mouse scroll actions, requiring a new type of input. Vertical and Horizontal scroll now use the same new input. (This is all done in the same way as Woof)

[rfomin]

I'm pretty sure we shouldn't allow using the mouse wheel for movement, it's considered cheating. Woof used to have a check for this: fabiangreffrath/woof#703 It was removed during the refactoring, and I didn't restore it, but Woof is not as strict as DSDA-Doom. We should at least ask on the speedrunning discord.

Also:

dsda-doom/patch_notes/v0.17.md

Line 12 in d965029

- Close an exploit in mousewheel input

[andrikpowell]

I'm pretty sure we shouldn't allow using the mouse wheel for movement, it's considered cheating.

I agree. Checking with the previous versions, the mousewheel up/down is disabled when it comes to movement or turning, and adding the new mouseb input type unintentionally removed that limitation.

I've since reverted the new mouse button type to use the traditional way input was dealt with. I can't seem to find the exact code that blocks the movement/turning specifically for the mousewheel, so this is my temp fix. On top of that DSDA has it's own input system that's quite a bit different from Woof, so going the Woof route may not be the best approach.

One thing we will be missing out on though is the mouse buttons having a delay tied to them. The most easiest way to see this was in movement/turning (even though we don't want this, it's a good test to see if the delay input is working as it should).

The best example of this is binding the automap zoom in/out to the horizontal scroll, as without the delay it is choppy instead of a short smooth gradual step. Although then again, I don't think there's many key actions where you would notice a difference between a gradual or instant input, besides movement/turning.