Several fixes here:

1. I realised after further usage and some extensive testing in more complex scenarios that JSON Arrays weren't handled correctly - they were always either masked at the whole field level (on Mask By Default mode), or left unmasked (on Show By Default mode). Now, the same settings that apply now also apply to nested objects inside arrays, or if the array contains primitives, the higher level array will apply. So for example, given:

address.firstLine

this will now apply to both:

{
  "address": {
      "firstLine": "value"
  }
}

and now also to all the firstLine values in an array type, too (this was not working correctly previously):

{
  "address": [
    {
      "firstLine": "value"
    },
    {
      "firstLine": "someOtherValue"
    }
  ]
}

Primitives will be handled as expected as well, where a filter like:

address.values

would now result that the following object:

{
    "address": {
      "values": [ "one", "two", "three" ]
    }
}

will correctly look like:

{
    "address": {
      "values": [ "xxxx", "xxxx", "xxxx" ]
    }
}

instead of the current:

{
    "address": {
      "values": "xxxx"
    }
}

which is currently losing the format, as well as non-sensitive information such as array length.

2. Some readability improvements & fixes, also updating tests to be uniform, so the exact same test code is not repeated. Now the JsonMaskerTest interface defines the core tests the input and output, with the ShowByDefault and MaskByDefault tests implementing the interface (with their own backing application.yml which makes them fit the test criteria) and have their own specific tests written in the class only

3. Small performance improvements, including defining the topic -> filtering keys in the constructor rather than constantly re-evaluating

4. Remove the phrase "Please contact akhq administrator" which is likely to cause confusion and bring people here, when the issue isn't AKHQ but that a record has not fulfilled the criteria for masking