refactor: remove input validation from MoveToInput

[dw-0]

Solves the following problem:

The input was validated against position_min and position_max of the configuration file. If the input falls below / exceeds the boundaries set inside the config, a visible error would be shown.
The real issue is, that those errors are also shown if there wasn't input from the user. The culprit in that case seems to be Klipper. The error was often reported, but wasn't possible to reproduce but looked like this:

It is suspected to be a rounding error in Klipper, hence Klipper actually reporting the wrong toolhead position which then appears to exceed the position_max by 0,01 which is enough to trigger an error during the validation methods. This often led to confusion for the user because the error simply was not comprehensible.

So the current solution aims at removing all validation from that component to reduce confusion.
As a trade-off Move out of range errors are then only logged in the console after submitting a move command.

Signed-off-by: Dominik Willner [email protected]