Re-organization of the CI/CD environments and dev boxes

Following up changes to how FOLIO front-end code is organised (platform-core, platform-complete, stripes-framework) and how it is versioned our CI/CD will need to be altered to be better suited for supporting ongoing development, testing and review work.

• John has proposed we focus on "released" artefacts and use the master branch of platform-complete to track only released artifacts (of UI modules). This branch could form a basis for new FOLIO CI environment called "folio-releases".

• UI modules release cycle could be made more granular to allow for the the "folio-releases" environment to be more up-to-date

• UI module release management will include strict approach to versioning backend dependencies (okapiInterfaces) to allow folio-releases environment to operate with released-only backend artifacts

• UI module code (NPM/yarn) dependencies versioning will be simplified through the use of stripes-framework

Detail will be captured in a document and link to this issue.