[9.x] Fix consistency of assertJsonPath to act like assertSame so that expected value be first parameter

[AhmedHelalAhmed]

This PR fix consistency of assertJsonPath to act like assertSame so that the expected value be the first parameter

// Take expected value first then the key
assertJsonCount($expected, $key)

// Take expected value first then the path
assertSame($expected, $path)

// So why we don't make assertJsonPath take expected as first parameters to be consistent 
assertJsonPath($expected, $path)`

[kylekatarnls]

For the record the failure here is not related to the current changes.

These would be fixed by #38852

[AhmedHelalAhmed]

@kylekatarnls Thank you for the clarification

[taylorotwell]

Thanks for your pull request to Laravel!

Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.

If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!

If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.

[AhmedHelalAhmed]

@taylorotwell
This modification mentioned by @themsaid in the stream in https://youtu.be/4yuVKMUnOf8 in Laravel official channel
and I'm happy to contribute to my favourite framework I mentioned to not duplicate the work and it's fine
Thanks