Remove position and momentum caching from pattern parameters
The caching mechanism was originally introduced in !37651 (merged), and was necessary to allow that merge request to happen. However, it bring with it a performance regression described in ATLIDTRKCP-301. As of the merging of !38077 (merged), the caching mechanism is no longer necessary and can be removed, which is exactly what this merge request does. This should restore the CPU performance to the level it was at before !37651 (merged). This merge request also means the class is completely free of mutable variables or thread safety risks.