Add real report generation

[eidolonpg]

Need to beef up the report - obviously - now that we have a good amount of raw data... aka actually generate a viable report.

[eidolonpg]

@theabraxas what's the priority on this? We have a couple of bugs and a few good enhancements on the table, but all of that relates to raw data. The report is nice but I'm not sure if that's what the current audience needs -- what's your opinion? I'll adjust my plans accordingly

[theabraxas]

IMO, if we make a 'cheatsheet' of the good data places in README, that would be enough for pentesters as the data is there, you just have to find it.

I think we want to look at the long-term goal of the project and decide if 'do we want to eventually move to a database-style of data storage and, if so, how soon can we do that?' Once we know that, we can decide if it's worth waiting until the DB is integrated and build our reports from there OR if it'd be better to build something passable now and then rebuild it when we switch to a DB model?

I don't know what time estimations would be on reports as-is but I would say we either want a database integrated or report output by the next time we demo the tool at a conference or something like that.

[theabraxas]

As of last conversation Toshi or eidolonpg will be working on building out a report by end of year or start of 2017