Consecutive -language:... Compiler flags in using options are ignored

[crater2150]

Version(s)
1.0.6

Describe the bug
If two -language: flags appear next to each other in a //> using options directive, the second one is ignored. The different behaviour is not reproducible by calling the Scala 3 compiler directly.

To Reproduce

I stumbled upon this while encountering a bug where strictEquality breaks if -Yexplicit-nulls is enabled, so that is what the examples use:

def repro[A](as: List[A]): List[A] =
  as match
    case Nil => Nil
    case _ => ???

This code causes a compile error, if compiled with scala3-compiler (version 3.3.1) and any of the following flag orders:

-Yexplicit-nulls -language:strictEquality
-language:strictEquality -Yexplicit-nulls -language:fewerBraces
-Yexplicit-nulls -nowarn -language:strictEquality
-language:strictEquality -language:higherKindedTypes -Yexplicit-nulls 
-language:strictEquality -Yexplicit-nulls -language:higherKindedTypes 
-Yexplicit-nulls -language:higherKindedTypes -language:strictEquality
-language:higherKindedTypes -language:strictEquality -Yexplicit-nulls 
-Yexplicit-nulls -language:fewerBraces -language:strictEquality

Compiling with scala-cli compile, the behavior is the same for the first five, but the last three compile without error, e.g.

//> using scala 3.3.1
//> using options -Yexplicit-nulls -language:fewerBraces -language:strictEquality
def repro[A](as: List[A]): List[A] =
  as match
    case Nil => Nil
    case _ => ???

To run all of the above compilations of flags, I used this script: https://gist.github.com/crater2150/4950128bbde80437d0ba6077fd94f805

Expected behaviour

-language:... flags should work without other flags between them.