[REGRESSION]: client-provided arguments to electron is at the end of argv list

[Maddobun]

We used to have this PR #16782 which addresses this issue #16614.
It looks like this change was lost over the course of a few commits on the same file.

[yury-s]

This regressed in #18804. We cannot directly pass user arguments first as playwright may use custom loader which goes as the first option and also expects certain options order, we ned to change that.

[yury-s]

@Maddobun what arguments do you see before yours? Looking at the code, it seems that most of the time it should be just your custom args but sometimes on linux --no-sanbox could appear first, is that what you observe? Also which playwright version are you using?

[Maddobun]

@Maddobun what arguments do you see before yours? Looking at the code, it seems that most of the time it should be just your custom args but sometimes on linux --no-sanbox could appear first, is that what you observe? Also which playwright version are you using?

I'm on 1.41.1 and in process.argv of my own electron app I'm seeing both --inspect=0 and --remote-debugging-port=0 between the executable path and my provided args.