Detect and handle webpack module cycles

[vojtechszocs]

This PR attempts to get a handle on the situation around circular module dependencies.

When running yarn check-cycles, module cycles are detected via CircularDependencyPlugin and subsequently handled at emit phase via ad-hoc HandleCyclesPlugin.

Cycle report is written to frontend/.webpack-cycles file.

Example cycle report:

# webpack compilation e656e6844f982012ba0f built at 04/01/2020 15:39:26
# this file is auto-generated on every webpack development build

# 168 total cycles: public (97), packages (71)
# 31 minimal-length cycles (A -> B -> A)

/home/vszocs/go/src/github.com/openshift/console/frontend/public/redux.ts
public/redux.ts
-> public/reducers/features.ts
-> public/module/k8s/index.ts
-> public/module/k8s/resource.js
-> public/co-fetch.js
-> public/redux.ts

... rest of cycle entries ...

Cycle report analysis:

• we have a very high number of cycles (and it keeps increasing over time)
• we have a relatively high number of A -> B -> A cycles

cc @spadgett @christianvogt

[vojtechszocs]

Note, this dependency was introduced in #1456 (unused until now).

[christianvogt]

/lgtm

[spadgett]

/approve
/retest

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: christianvogt, spadgett, vojtechszocs

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [spadgett]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment