Consider option to only install PeakRDL CLI without core plugins

[amykyta3]

Splitting this into a separate request described by @Risto97 in #17:

Did you think of separating peakrdl from all of the plugins, so they are not installed when installing peakrdl.

To illustrate my use case, I am using peakrdl-html, peakrdl-regblock and two of my plugins, but I am not using the rest of > the toolchain. I am invoking the tools sometimes from python script or cmake wrappers for peakrdl.
This way the unnecessary dependencies get pulled into my virtual environment.

[amykyta3]

In most cases I want to publish PeakRDL as a complete tool that is ready to use out-of-the-box. However I can see the value of pruning it down to a more lightweight install in some cases.

Will look into what mechanisms, if any, allow something like this.
One option would be to publish a separate package that only includes the CLI component, but I'm not too keen on breaking this project apart further as it creates dependency pains. Will look into whether there are cleaner ways to accomplish this.

[Risto97]

I like the solution of separating the CLI component.

This way you can fix the PeakRDL-cli version to the plugins that are compatible.