Create tool to identify and visualize circular imports between plugins

[joshdover]

In order to add support for TypeScript project references and Bazel builds to plugins on a per-plugin basis, we cannot have any circular imports between plugins.

Since this is a blocking issue to solving many of the performance problems with our current developer experience & tooling, we should build a tool to identify the circular imports between our plugins so that we can determine the granularity of projects, where circular imports can easily be removed, how much effort will be required to resolve this problem.

Possible tools that could help us:

• madge
• dependency-tree (which madge is based on)

Related to #71566 #46773 #69706

[elasticmachine]

Pinging @elastic/kibana-platform (Team:Platform)

[elasticmachine]

Pinging @elastic/kibana-operations (Team:Operations)

[mshustov]

The last time I tried to use madge to detect circular refs in the platform codebase, it didn't work because Kibana uses a newer TS version, so I had to switch to https://github.com/sverweij/dependency-cruiser (my mistake, madge doesn't use that one under the hood)

[dplumlee]

I know @oatkiller had worked on something similar to this problem within the security solution plugin in this pr #75579 to help with circular dependency visualization. Might be loosely related enough to lend insight