Add a new extension that adds the new path options

This parameter is not used any more because the configurable path printer service takes care of handling path printing

And now this function is not needed

We inject the new service into the classes that need it

New config option to set this option using PHP

And new yaml to php converter for this option

This is the new service that prints paths, adding an option to decide if they should be printed as relative (default) or absolute

I'm a little nervous that there might still be a BC impact with some of these classes if they're used by extensions / formatters and:

• They aren't taking them through our service container, so this method doesn't get called and class fails attempting to call the ->configurablePathPrinter
• They are using our service container definitions, but decorating our class, so this method won't be defined on their decorator and the service container will throw on attempting to create the service.

I wonder if we can make this safer.

Perhaps if we instead add this as an optional constructor parameter with a fallback instead of a setter - e.g. like this:

public function __construct(
        private ResultToStringConverter $resultConverter,
        private ExceptionPresenter $exceptionPresenter,
        private TranslatorInterface $translator,
        string $basePath,
        ?ConfigurablePathPrinter $configurablePathPrinter = null
) {
        $this->configurablePathPrinter = $configurablePathPrinter ?? new ConfigurablePathPrinter($basePath, printAbsolutePaths: false);
    }

Then I think:

• If people are doing new ListPrinter(...) it will continue to work exactly as now, it just won't respect the new config option
• If people have decorated our class without changing the constructor args, they'll get an extra argument that is not in their constructor signature and ignore it
• If people have decorated our class and changed the constructor args, they will get the same class / args as before

What do you think?