Simplify project structure and align it with patternfly-react standards

[vojtechszocs]

• split dependencies vs. devDependencies, remove deps we don't need, align deps with patternfly-react and oVirt UI projects (ovirt-engine-ui-extensions, ovirt-web-ui)
• simplify webpack (dev/prod) configs and Jest (test) config
• align ESLint rules with patternfly-react standards, try to use eslint-plugin-patternfly-react
• simplify project's scripts like yarn build etc. (use CLI where appropriate)
• ensure recent versions of deps, i.e. yarn outdated
• document common project conventions in Storybook, using Foreman as the reference
• document developer workflow and other important stuff in README

[mareklibra]

simplify webpack (dev/prod) configs and Jest (test) config

Makes sense but carefully - let's not deviate from create-react-app more than really required. IMO, it's better to keep "a few more useless" things than breaking the structure much. This approach might help us in the future when upgrading.

[mareklibra]

ensure recent versions of deps, i.e. yarn outdated

And establish a rule to run it at every beginning of new sprint

[vojtechszocs]

Makes sense but carefully - let's not deviate from create-react-app more than really required.

CRA adds lots of unnecessary complexity, both in terms of project's dependencies and its scripts & configuration, in my opinion. I'd like to use webpack v4 (latest stable) and minimize the config to the necessary minimum.

[kubevirt-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[vojtechszocs]

All checklist items except for developer docs are already done.

[kubevirt-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[kubevirt-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

[kubevirt-bot]

@kubevirt-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.