feat: analyzer

[peckto]

Adding a draft version of the gallia analyzer to analyze and visualize scan results.
Credit goes to @chanyoungso

Example usage:

$ poetry install --extras analyzer
$ poetry shell
$ gallia analyze -aer --source gallia.db

Open points:

• Load analyzer as optional gallia module to reduce loading time
• use penlog logger
• Mixin class for artifacts dir #221
• docs
• create mapping between vendor_lookup table and ecu

[peckto]

Because the information in the tables vendor_lookup and vendor_session are ECU specific and we can have results from multiple ECUs in one database, we need a mapping between the vendor specific information and the ECU.

To implement this mapping, we have two possibilities:

1. Create a "vendor_lookup_id" column in the ECU table (1:Vendor Lookup -> n:ECUs)
2. Create a "cross_vendor_lookup_ecu" table (n:Vendor Lookup -> m:ECUs)

My first guess would be (2), this is more flexible and we do not need to store vendor/analyzer specific information in the ECU table.

[rumpelsepp]

Poetry 1.2 is out. Maybe this helps with making the analyzer optional:

https://python-poetry.org/docs/pyproject/#scripts

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[peckto]

rebased to current master