Pact Foundation

Hi Team,
I noticed since updating my `pact-plugin-cli protobuf` version from `0.5.4` to `0.6.X` , the matchers aren't returning the rules for nested (inline?) repeated fields paths and hence validation seems to pass always ignoring those matching rules. I have an example up in <https://github.com/pact-foundation/pact-plugins/pull/89/files> where the contract passes for `0.6.0` (unintended) but fails for `0.5.4` ( as intended). Is this a possible regression or the am I missing something?

Meanwhile, I did create an issue for this in <https://github.com/pactflow/pact-protobuf-plugin/issues/231>.

i.e for
```message AreaResponse {
  repeated float value = 1;
  repeated NestedFieldLevel1 nestedFieldLevel1 = 2;
}

message NestedFieldLevel1 {
  string FirstLevel = 1;

  message NestedFieldLevel2 {
    string InnerLevel = 1;
  }
  repeated NestedFieldLevel2 InnerLevels = 2;
}```
I'd expect
```          "matchingRules": {
            "body": {
              "$.nestedFieldLevel1[0].FirstLevel": {
                "combine": "AND",
                "matchers": [
                  {
                    "match": "equality"
                  }
                ]
              },
              "$.nestedFieldLevel1[0].InnerLevels[0].InnerLevel": {
                "combine": "AND",
                "matchers": [
                  {
                    "match": "equality"
                  }
                ]
              },```
to fail on equality when there is a mismatch. That happens in `0.5.4` but not after `0.6.0`+