Clarify Lazy Services usage with final & readonly classes

[kiler129]

Since Symfony 7.3 lazy services support final and readonly objects:

% grep TaskGroups src/UseCase/CreateUser.php 
final class TaskGroups extends YamlConfig
% bin/console debug:container 'App\UseCase\CreateUser' 2>/dev/null | grep Lazy
  Lazy             yes

This works since PHP 8.4 allows for native lazy ghosts that don't need to extend the class:

final readonly class TestObject {
    public function __construct(public int $number) {
        echo "Constructor called\n";
    }

    public function getLucky(): void {
        echo "Your lucky number: $this->number\n";
    }
}

$lazy = new ReflectionClass(TestObject::class)->newLazyGhost(function (TestObject $object) {
    $object->__construct(\random_int(0, 100));
});
echo "Object created\n";
$lazy->getLucky();

The support for this feature was introduced in symfony/symfony@ed695a6 (precisely here). However, documentation still points users to use Interface Proxifying, regardless of the frameworks or PHP version.

[OskarStark]

This is not a warning anymore, make let's move this to a versionadded 7.3 directive?