Togglable inputs; toggle_duck, toggle_jump, toggle_sprint, toggle_walk

[braem]

Closes #921
Closes #923

• Adds toggle_jump, toggle_sprint, and toggle_walk commands.
• Unlocks toggle_duck from being ahop only.
• Locks toggle_jump to gamemodes with autohop
• Locks toggle_sprint and toggle_walk for gamemodes that have those (using GameModeHUDCapability)
• Moved toggle_duck into mom_player to better centralize the togglable inputs.
• Overrides PlayerRunCommand, appending inputs if they have been toggled on.
• Connected with the hud keypress display. Have to network all toggles besides duck for more accurate display.
• toggle_sprint and toggle_walk untoggle when player is stopped from sprinting/walking.
• Removed unused code from player and in_main & minorly fixed up the keypress display (OVERRIDE -> override, moving multi-line method out of class declaration, changed bgcolor to be an animation var instead of hardcoded).
• Added to keybinds:
  

Checklist

• I have thoroughly tested all of the code I have modified/added/removed to ensure something else did not break
• If there is a localization token change, I have updated the momentum_english_ref.res file with the changes, ran tokenizer.py to generate an up-to-date localization file, and have committed both the .res file changes and the new localization .txt file
• If I introduced new h/cpp files, I have added them to the appropriate project's VPC file (server_momentum.vpc / client_momentum.vpc / etc)
• If I have added or modified any visual assets (models, materials, panels, effects, etc), I have taken screenshots / videos of them and attached them to this PR directly (screenshots uploaded through github, videos uploaded to youtube and linked)
• If I have modified any console command, console variable, or momentum entity, I have opened an issue (or a PR) for it in the Momentum Mod documentation repository
• My commits are relatively small and scoped to the best of my ability
• My branch has a clear history of changes that can be easy to follow when being reviewed commit-by-commit
• My branch is functionally complete; the only changes to be done will be those potentially requested in code review

[braem]

Did the proposed change, nicely simplifies things. Also added a check for duck toggled in keypress hud to properly display that; captures the time between pressing and fully ducking.

[braem]

Implemented the requested changes. Also I found that the run safeguards are hit when inputs are toggled on, should this be the case? For now I changed it to only safeguard if the button is held down, not toggled.
Maybe a cvar?

[Gocnak]

I'm inclined to say yes; it's still movement keys, and they took the easy way out of toggling it instead of holding it, so I would expect it to behave as if they have it pressed (as does the hud_keypress panel).