Support passing ETISS plugins by path via command line or INI

[PhilippvK]

Currently ETISS plugins either need to be integrated in the etiss build or need a special procedure (https://github.com/tum-ei-eda/etiss-accelerator-plugins/blob/main/README.md) to be loaded at runtime.

Both approches (Define etiss_wd in INI, create PluginImpl dir, copy MyETISSPlugin.so into PluginImpl vs. edit list.txt file of ETISS install) are annoying. Would it be possible to (optionally) allow passing ETISS plugins by paths instead of by name?

Usage could look like this:

• Via run_helper.sh: /path/to/run_helper.sh build/main -ppath/to/MyETISSPlugin.so -ppath/to/MyOtherETISSPlugin.so
• Via INI and running bare_etiss_processor directly: /path/to/bare_etiss_processor build/main -icustom.ini using the following INI file:

  [StringConfiguration]
  etiss.extra_plugins=path/to/MyETISSPlugin.so,path/to/MyOtherETISSPlugin.so  # Comma as delimiter

The using approach for passing plugins by name would of course still be supported (-pMyETISSPlugin or [MyETISSPlugin])

CC @wysiwyng

[PhilippvK]

We got a spam/bot/maleware comment under this issue. I have just reported and removed the comment.