bug: "Input Variable" event command should not allow boolean variable selection

[AlexVild]

Describe the bug
If you use the Input Variable event command with a boolean-type variable, you will be given a dialog menu with no input field. Neither selection in the menu changes the variable's value - seems to imply that booleans shouldn't be available for selection for this command.

Version Encountered

7.0 Stable

To Reproduce
Steps to reproduce the behavior:

1. Make a boolean player variable
2. Make an event that uses "Input Variable" event on that var
3. You can try to change the var in the event, but it will not do anything to the variable's value.

Expected behavior
I propose just not allowing input variables to be of type boolean.

Screenshots

Neither option changes the variable's value.

[WeylonSantana]

Just bringing thoughts, I would say it's actually easy, just create a bool "isString" and a checkbox in the input editor, if you check cmbVariavel it will only show variables of type string, if not, only variables of type number.

I would do that, but there is the issue of migrating to all existing games that already use the inputs, for guilds and so on, all the indexes would be wrong, so I'll pass =D, but there's a simple alternative above, the complicated thing is just the migration