Prevent creating non-existent models from container

[ralphjsmit]

Currently, the closure evaluation system works great by resolving any dependencies not provided by name or type from the container. This is very useful. However, there is one situation where it isn't useful and that is when it is evaluating empty/non-existent Eloquent models from the container.

For example, in Filament V3 we had the nice feature of being able to type an Eloquent model as both User $record and User $user, which would both work nicely. However, sometimes there are situations where you think you have a $record, but actually for some reason you don't (or you have a different type of record when working with eg relationships or repeaters). If you would then still type it as User $user, you would get an empty/non-existent Eloquent model from the container. This has caught me in very complex forms out quite a few times and therefore I generally prefer User $record now just for this, whilst for the cleanliness I would prefer User $user.

This PR fixes the issue by preventing the container from instantiating an empty Eloquent model if it was not able to resolve dependency using type or name. This prevents users from typing things like User $user, thinking they have the record but they actually don't. It should not really impact users, as no one would instantiate their empty models using the container and would only help to prevent bugs. I also added a test to prove the behavior.

Thanks!

[ralphjsmit]

There are some changes in un-touched files because of Pint.

[danharrin]

If the model has been bound to the container manually, we should still resolve it. Someone might want to bind the current tenant to the container for easy access, for example.

[ralphjsmit]

Good point, changed!