feat: autoconfigure interfaces

[soyuka]

The idea of auto-configurable services is that you setup some interfaces for auto configuration and they get automatically tagged by the Laravel container. For example, let's take this interface:

interface ProviderInterface {}

We want this interface to be automatically tagged in the container, a Laravel component would have something like this:

$app->make(LibraryProvider::class, function(Application $app) { 
    return new Provider($app->tagged(ProviderInterface::class)); 
});

$app->autoconfigure(ProviderInterface::class);

With this feature, in userland developers don't need to do anything as these services are automatically discovered and tagged.
We implemented this into API Platform and @TomasVotruba suggested I propose this to the Laravel framework.

Do you think that this is something we'd like to see inside the Laravel framework?

[soyuka]

This is definitely going to be an issue if the discovered file is a blade template or a pest unit file. Still looking to improve that...