User provided JsonPaths should be trimmed as early as possible

I noticed defensive calls to `String.trim` actually trimming the JSON path in a profile from a user, where these paths come from ingestion transformation configuration.

This means that:
* the JSON path is trimmed at least once per ingested row, creating unnecessary allocation pressure
* the lookups for cached compiled `JsonPath`s always uses a new `String` object, which means the JSON path's hash code is calculated at least once per ingested row.

Cleaning JSON paths before initialising the record transformation would remedy this.

Start by locating record transformation initialization and the ingestion path where user-provided JSON paths are trimmed and cached. Done means configured paths are cleaned before ingestion, with equivalent lookup behavior and no per-row trimming or repeated path allocation; add or update focused tests if the relevant test area is found.

Written by the indexing model from the issue text.