Test-specific extension is overridden by project-level extention

[OliverO2]

Kotest master, as of commit 45df9ae

Following up from #3602 (comment):

I am currently working on enabling nested invocations for the BlockHound extension. The following will not work:

@DoNotParallelize
class BlockHoundSpecTest : FunSpec({
   extension(BlockHound())

   test("detects for spec") {
      shouldThrow<BlockingOperationError> { blockInNonBlockingContext() }
   }

   // other tests...

   test("nested configuration").config(extensions = listOf(BlockHound(BlockHoundMode.DISABLED))) {
      shouldNotThrow<BlockingOperationError> { blockInNonBlockingContext() }
   }
})

In the above case, the test-specific extension BlockHound(BlockHoundMode.DISABLED) will be overridden by the project-level extension BlockHound(). The cause seems to be an incorrect extension processing order. I am just preparing a PR to fix this.

[sksamuel]

This is fixed by #3614