Resolves #44

Cache Recorders are being migrated to a different service to change how
pagination headers are cached or generated. The test that is being
removed was very brittle and not very useful.

Our pagination data is tied to the recorder cache, which was doing
imperfect lookups of the cache keys and comparisons, and was failing
sometimes to find matching data. This should make the calls more
accurate at least, if not fix the issue.

Tested internally, these headers will give better support for rewrites
as we typically operate behind a reverse proxy. When not behind a proxy,
the API still operates as expected without any hiccups.

Resolves #34

Current code will fail if the query string starts with the page data.
This should address this issue, and also adds testing to help guard
against regression.

We use strict management of persist contexts, so keeping entities
attached while we work just creates collisions as we update records.

Pagination was causing failures for native endpoints which were used in
verifying some of the endpoints downstream. Added refresh or alert when
clearing cache keys

Startup proxy service broke 2-3 of our development patterns and it was
missed in review. These issues were fixed as part of this PR and will be
included in next version.

Zachary Sabourin authored Nov 22, 2022 and Martin Lowe committed Nov 23, 2022

Resolves #29

Zachary Sabourin authored Nov 10, 2022 and Martin Lowe committed Nov 10, 2022

Resolves #25

To make code more maintainable, we've started to use sonar to better
pick up some of the small errors that might make the code harder to
maintain.

Resolves #19

Resolves #20

Resolves #18