doom: Fix key_menu_forward in Crispness menu

[mikeday0]

key_menu_forward should behave like key_menu_right for enum items in the Crispness menu.

Trying to correct a dumb oversight from the last time I touched this code. 🤦‍♂️ Better late than never!

[fabiangreffrath]

Thanks for this! While at it, I had a hard time merging your latest changes to joystick input from chocolate-doom/master lately and still couldn't get it to finish. So, if you wouldn't mind helping to merge these changes into Crispy, that'd be appreciated.

[turol]

@fabiangreffrath Try https://github.com/mhagger/git-imerge

[mikeday0]

Thanks for this! While at it, I had a hard time merging your latest changes to joystick input from chocolate-doom/master lately and still couldn't get it to finish. So, if you wouldn't mind helping to merge these changes into Crispy, that'd be appreciated.

Sure, I'll give it a go.

[mikeday0]

I've got all the joystick/gamepad and other changes merged locally and everything seems to be working correctly. I wanted to check with you about the CI changes - are those okay to merge? msys2.yml gets deleted and all of its contents are instead incorporated into main.yml. Also there are two main.yml conflicts needing resolution:

1. name is 'Continuous Integration' in upsteam, 'build' in Crispy
2. "**.yml" is removed from paths-ignore in upstream.

Any suggestions?

[fabiangreffrath]

@rfomin can we take over all CI changes from upstream into Crispy?

[rfomin]

@rfomin can we take over all CI changes from upstream into Crispy?

Yes, sure. I can make a PR.

[rfomin]

name is 'Continuous Integration' in upsteam, 'build' in Crispy

I think it should be named 'Continuous Integration'.

"**.yml" is removed from paths-ignore in upstream.

I have edited workflow files many times in a row and made this exception and then forgot to remove it. So I think that the "**.yml" exception should be removed.