Laravel Service Container: Am I doing the right thing?

I have an invokable action class called: AttachMembersToRoom . Now, aside from basic form request validations, I also have complex validation, like comparing values across members, identify overlapping member rooms, and more... so I decided to make each validations into custom invokable classes, like CompareMembersValues, IdentifyOverlaps , and more....

At first, I did the following to execute every validations in AttachMembersToRoom :

class AttachMembersToRoom
{
    public function __invoke(MyData $data)
    {
        foreach ($this->validators() as $validator) {
            $validator()($data);
        }

		execute main logic here...
    }

    /**
    * @return callable[]
    **/
    private function validators(): array
    {
        return [
            fn () => app(CompareMembersValues::class),
            fn () => app(IdentifyOverlaps::class),
            ...
            ...
        ];
    }
}

but looking at it, I think it's a bit excessive to use app() for every validators I have, and I'm afraid that the whole "attaching members to room" process would take up much memory than it should be.

so I decided to bind-tag it in the service container, like so:

$this->app->tag([
    CompareMembersValues::class,
    IdentifyOverlaps::class,
], 'memberValidators');

and in AttachMembersToRoom , I made the following adjustments:

class AttachMembersToRoom
{
    public function __construct(#[Tag('memberValidators')] protected iterable $memberValidators) {}

    public function __invoke(MyData $data)
    {
        foreach ($this->memberValidators as $validator) {
            $validator($data);
        }

		execute main logic here...
    }
}

At this point, I'm not even sure if I'm doing the right thing, or am I even overcomplicating things?

But my goal for all of this is the testability.. at some point, I want to mock each of these validators, and bypass some of these validators during testing.