Fix Closures in MaxValue and MinValue

[remiebelingmerifond]

I encountered issues similar to #72 when trying to inject a service into a closure passed to the minValue method.

I compared the MoneyInput::minValue method with its counterpart in TextInput::getMinValue and noticed that $this->evaluate($value) was being called too early in the MoneyInput implementation.

This was what caused the Typed property Filament\Forms\Components\Component::$container must not be accessed before initialization Error.

As the closure is evaluated in TextInput::getMinValue anyway, there seems to be no need for minValue or maxValue to evaluate $value at all.

So i aligned the way minValue and maxValue works to the way TextInput does it.

After these changes:

• Closures that depend on Laravel's dependency injection or Filament's closure injection features work correctly.
• Passing integers values remains fully functional.
• Issue gte and lte support #72 is very likely resolved

[pelmered]

This looks good. Thank you very much for your contribution!

[pelmered]

And don't worry about Scrutinizer. It didn't play well with Pest for test suite so I removed it now.