Added new JsonPath condition

[manofearth]

Add JSON Path request condition filter

This PR adds a new feature that allows filtering requests by checking values in specific JSON paths of the request body. This is particularly useful when you need to match nested JSON structures in requests.

Changes include:

• Added JsonPathCondition class for handling JSON path request matching
• Updated documentation in README.md with JSON Path feature description and examples
• Added tests to verify JSON path matching behavior

The feature supports all standard matchers (isEqualTo, matches, contains, isSameString) and uses simple dot notation for specifying JSON paths. Use cases include:

{
    "user.address.zipCode": { "isEqualTo": "12345" }
}

All tests are passing

[mcustiel]

@manofearth Many thanks for this great improvement. Please check the broken integration tests: https://scrutinizer-ci.com/g/mcustiel/phiremock-server/inspections/d23a5f44-8028-4b4b-bee5-e7787f679fae
When it's fixed I will approve because this looks awesome.
I love this new feature. Again, thank you very much.

[mcustiel]

[question] From the code I assume we can also use notation like: users.0.name in case of indexed arrays. Is that correct? If yes, it would be nice to document it and have a test for it.

[manofearth]

You are absolutely right about array access notation - users.0.name will work for accessing array elements. I will add documentation and test to demonstrate this functionality.

[manofearth]

@mcustiel Thank you very much for such a positive feedback! I'm really glad you find this feature valuable.

About the failing tests - I believe the issue is related to the dependency on phiremock-common package. I have created a separate PR there with the necessary changes to support jsonPath matching: mcustiel/phiremock-common#17. The tests are failing in scrutinizer most likely because it's still using the old version of phiremock-common without jsonPath support.

Here's what I propose:

1. First merge the PR in phiremock-common repository to get the jsonPath support in place
2. I will add documentation and test showing array access examples like users.0.name
3. After that, we can rerun scrutinizer tests for this PR (unless they rerun automatically when I push the documentation commit)

Does this plan work for you?

[mcustiel]

@mcustiel Thank you very much for such a positive feedback! I'm really glad you find this feature valuable.

About the failing tests - I believe the issue is related to the dependency on phiremock-common package. I have created a separate PR there with the necessary changes to support jsonPath matching: mcustiel/phiremock-common#17. The tests are failing in scrutinizer most likely because it's still using the old version of phiremock-common without jsonPath support.

Here's what I propose:

1. First merge the PR in phiremock-common repository to get the jsonPath support in place

2. I will add documentation and test showing array access examples like `users.0.name`

3. After that, we can rerun scrutinizer tests for this PR (unless they rerun automatically when I push the documentation commit)

Does this plan work for you?

Sounds good. I also think that the broken tests were related to the unmerged changes on phiremock-common. I approved your PR there and merged it, so the build can maybe use the latest release.
Additionally, thank you very much for the fix to run the tests on windows. I was missing help there :)

[manofearth]

@mcustiel Thank you again for the positive feedback and quick response!

I've added documentation and tests for array access notation. However, the tests are still failing but for a different reason now - it's related to PHP 7.2 compatibility. I accidentally left a trailing comma in a parameter list in phiremock-common which is not supported in PHP 7.2.

I've created a fix in PR mcustiel/phiremock-common#18 to address this issue. Could you please review and merge it? After that, if you could restart the scrutinizer build for this repository (phiremock-server), the tests should pass successfully.

[mcustiel]

Great Job. Thank you very much

[manofearth]

@mcustiel Thanks for the quick turnaround in approving this PR! One last puzzle piece remains - would you please review this PR to phiremock-client which adds the corresponding jsonPath support to complete the feature?