fix: refactor Input handling

[fcolarich]

What does this PR change?

What does this NOT do?! well for starters, it wont cuddle you in the middle of the night when you are feeling lonely.

What does DO do? Given the growing number of windows and menus and whatnot that we are adding, the input handling was getting out of control, particularly blocking and unblocking input. It would happen that a window would block input until closed and then another window would open blocking the same input, but when the previous window finishes closing after the second one loads, it blocks the input again. And all sorts of similar things. Making it REALLY difficult to ascertain which inputs should be enabled and when.
To avoid this, I piggybacked into a couple of existing systems that already handled input changes, but improved them so we can properly track how many times each input was requested to be blocked or unblocked.
So, I expanded the InputBlock class so it can be used as intermediary between the already existing InputMapComponent and every Controller. Also I expanded the InputMapComponent so it has inside a dictionary tracking each input kind along with the number of block requests for it.
The InputBlock class can block several inputs at the same time, making use of the InputMapComponent.Kind Flag enum, but can be overriden to only block one input to save a bit of processing.
The InputMapComponent will only update its Active property when the block counter reaches either 1 or 0 (for disabling or enabling the inputs), in other cases it will just increase or decrease the appropriate counters.
Other than that, it was a matter of updating all places where input blocking/unblocking was done and make sure the number of blocks and unblocks was paired in all cases. This was time consuming for some parts of the game, but overall ended up improving some exit flows as well.
Also, added finally, the input blocking while the loading screen is showing, this way no input will be sent while displaying it.

Now, go find something to cuddle you in the middle of the night you brave soul!

How to test the changes?

To test it just try to go through the normal flow of the game, chat messages, menus, jumping through worlds, etc. The input should behave as before and even better :) Now it should be impossible to move while teleporting and the loading screen is showing for example.
This fixes this issue as well: [https://github.com//issues/1793] As it was caused exactly by this kind of Input woes.
Also fixes an issue happening when opening the emote wheel and closing it quickly which sometimes would leave some inputs blocked

[github-actions]

New build in progress, come back later!

[anicalbano]

🟢 Tested thoroughly, everything appears to be working as expected

[davidejensen]

Niceeeee

[popuz]

Nice refactoring 💪
However, I would suggest some changes here and there :) While most of them are small and rather cosmetical, changing BlockInput/UnblockInput from UnblockInputs(InputMapComponent.Kind kinds, bool singleValue = false) to UnblockInputs(params InputMapComponent.Kind[] kinds) could be a nice improvement

[fcolarich]

Will think of more optimizations for the block/unblock methods after merging :)