SPIKE: Investigate and define latest cache-enabled OKAPI migration steps

It is required to clarify the following questions:

1. Does new OKAPI support per-request cache disable option that can be switched ON via HTTP header.
2. Does stripes-connect manifest config support custom HTTP headers and if yes then how to pass it and in which config section.
3. If OKAPI cache is not configurable in request itself then we should find out how can we switch cache off at all.

Then if Points 1 and 2 is true we should review all our manifest configs in all the UI modules to define which of them require cache to be switched off and disable it for those requests.

In case it's helpful: Here is a file change in git: https://github.com/folio-org/okapi/pull/879/files, plus see attached notes