[Bug]: Overriding parent tests gives TestCaseAlreadyInUse

[riabiy]

Hi. I can be missing something and I believe it's a bug, nevertheless.

What Happened

Any attempt to override any parent test class gives me TestCaseAlreadyInUse.

Same thing happens both for pest()->extend(SpecificTestCase::class) in the test file and in the Pest.php file.

How to Reproduce

//Pest.php

pest()->extend(DuskTestCase::class)->in('Browser');
//can be in the Specific/AnyTest.php or in the Pest.php, both give same result
pest()->extend(SpecificDuskTestCase::class)->in('Browser/Tests/Specific'); 

Sample Repository

No response

Pest Version

3.4.1

PHP Version

8.3.7

Operation System

macOS

Notes

If this is the desired behaviour, what is the recommended way to override parent class for very-very 1-time niche cases?
In PHPUnit it's just vanilla PHP.
Creating a folder with "PestCanNotOverridePlaceHere" is a bit meh and not Laravelish enough, IMHO.

[riabiy]

Could be a duplicate of #1109 and related to #765.

[riabiy]

The issue persists. I'm not demanding anything by any means, just want to understand, if it's a design decision and, if so, what is the way to have DatabaseMigration on some tests and LazyRefreshDatabase on tests in the same folder?
They belong to the same scope, domain, etc. Just sometimes in rare cases we care about order of IDs to make snapshot smoke tests easier.

And, overall, it was something, that was working just fine in PHPUnit (due to the class-based approach), so I assume we want PestPHP to behave the same to make it a drag-n-drop replacement with better syntax. Unless I'm missing something.

[riabiy]

Still present. Bumping it slightly up, so it's not abandoned, though I don't want to spam it too.
As respectfully, as I can ; D