Route segment constraints should be inferred by controller method signatures

[innocenzi]

Description

For instance, this:

#[Get('/foo/{id}')]
public function __invoke(int $id): void
{
    dd($id);
}

Should not trigger this error:

Instead, it should 404 just like /foo/{id:\d+} would do.

Benefits

It would be a better experience for end users to get 404s in those situations than 500s.