replaceValues in config files only works at top level

For example,

```
{
"folio_field": "totalEstimatedPrice",
"legacy_field": "FOLIO_totalEstimatedPrice_SYSTEM_AUD",
"value": "",
"rules": {
"regexGetFirstMatchOrEmpty": "[0-9]+\\.[0-9]{2}"
},
"description": ""
}
```

works, but

```
{
"folio_field": "ongoing.isSubscription",
"legacy_field": "FOLIO_ongoing_isSubscription",
"value": "",
"description": "",
"replaceValues": {
"TRUE": true,
"FALSE": false
}
}
```

doesn't

Start by locating the config-file handling for replaceValues and compare how the top-level example is processed with the nested ongoing.isSubscription example. Done means the nested replaceValues mapping applies TRUE and FALSE as shown in the issue.

Written by the indexing model from the issue text.