89 confirm upgrade, reset Yarn

What's included

• chore(toolbarSort, filterReducer): updates for lint

  
* lint updates

• fix(build, readme): 89 yarn.lock regen 
* yarn.lock regen, event-stream package compromise

  • confirm docker build uses latest yarn version
  • readme updated

• ~~chore(readme): 89 updated yarn
~~

  • confirm docker build uses latest yarn version
  • readme updated

• ~~chore(oc setup): remove local run oc references
~~

  • update README local run links
  • remove non-functional oc references

• ~~chore(build): update create react app
~~

  • upgraded create react app react scripts, build packages
  • removed chokidar in favor of node sass, per documentation
  • sass background image paths updated for login screen
  • minor prettier syntax updates toolbarSort, filterReducers
  • yarn-lock regen, event-stream package compromise

Notes

Additional updates were added to help correct build errors

• appears upgrading to the react scripts caused some out of memory issues, possibly on the webpack side of things. we trimmed the mr down to the essentials
• build packages around create react app
• removed unused/broken oc scripting in favor of the review scripts
• regenerated yarn.lock due the event-stream compromise, https://blog.npmjs.org/post/180565383195/details-about-the-event-stream-incident

Also it appears the lastest yarn has been "automanually" updated for both GitLab CI and the Docker yum install script

How to test

• For package updates a simple local run, and confirmation check of the review environment running should be adequate

  For review, you'll need a login, or access to a Cloudigrade instance.

  1. Clone the updates locally, then
  2. From the terminal, within the repo context, run $ yarn start:review
  3. You may need to log in, do so

  The mock dev setup can be used to help a quick confirmation.

  1. Clone the updates locally, then
  2. From the terminal, within the repo context, run $ yarn start
  3. You may need to log in, do so
     • Note: the local dev server will take any combo of email/made up password to log in

• Confirming the yarn package is at 12.3+ you'll need to review the pipelines/gitlab ci aspect, something like

  • https://gitlab.com/cloudigrade/frontigrade/-/jobs/128094687
  • https://gitlab.com/cloudigrade/frontigrade/-/jobs/128094688

  

Updates issue/story

Updates #89 (closed)