[Feature]: Handle nested fields in matchers excludedKeys

[williamgarr]

Pre-flight checklist

• I searched existing issues and this feature has not been requested yet.

Problem Statement

Hello, in a test I made, I needed to ignore a nested field in my output message and tried the following syntax RootField.NestedField but it didn't work.

Is it possible to study the possibility to handle this behaviour for excludedKeys ?

Proposed Solution

Then expected record from file based on schema
      | topicAlias    | file                                 | expectedRecordKey         | excludedKeys                |
      | my-topic     | test.json                         | TestKey                            | RootField.NestedField   |

Alternatives Considered

No response

Affected Component

Cucumber / BDD Integration

Example Usage / API Sketch

Additional Context

Avro schema example :

{
      "name": "RootField",
      "type": [
        "null",
        {
          "name": "RootField",
          "type": "record",
          "fields": [
            {
              "name": "NestedField1",
              "type": [
                "null",
                "string"
              ],
              "default": null
            },
            {
              "name": "NestedField2",
              "type": [
                "null",
                "string"
              ],
              "default": null
            }
          ]
        }
      ],
      "default": null
    }