Reference environment builds broken 2020-09-29 -- upgrading to okapi-4

FYI @Adam Dickmeiss, @David Crossley's comment that the UI functions notwithstanding, in fact the UI is severely crippled by lack of access to /_/proxy/tenants/$tenant/modules. @Marc Johnson suggested this could be the case last week and @Anna Melnyk confirmed it today.

In other words, although the rest of the UI isn't showing error messages, it is wrongly assuming that all data behind an optional-okapi-interface is unavailable.

With today's build we can now login as diku_admin, but the "Settings" page for "UI modules" is total red. Also says "Version Unknown" for Okapi.

Also:

Users search and view does seems to be working properly.

So it seems like progress, and maybe just a new permission needed by the Stripes facility that presents the Settings.

Looking via the backend, docker logs for mod-authtoken is full of "SEVERE: Unsupported JWT format" (not sure if relevant).

With the resolution of https://folio-org.atlassian.net/browse/OKAPI-907#icft=OKAPI-907 and the release of okapi 4.1.5, I have unpinned Okapi. The next set of reference builds will include Okapi 4.1.5. A test build of folio-snapshot is currently available at https://folio-snapshot-test.dev.folio.org.

@John Malconian will you a get a chance to try Okapi 4.1.5 today and see if it fixes this problem?

Hopefully with release of Okapi 4.1.5 the CORS issue will be fixed. CORS is handled by Vert.x before "normal" proxy operation of Okapi is even started. That's why the log is silent about this. Created https://folio-org.atlassian.net/browse/OKAPI-908#icft=OKAPI-908 for that work.