some major redesign to simplify the implementation of the persistence layer. All the logic for capturing the build info is no longer in the repo, and since we are only saving at the end of the build this will cut down on the number database calls.
dropped the 'result' column of the plugin execution since I believe for a build to pass all plugins would had to execute successfully. The only thing I am not sure of is if a plugin can be "SKIPPED" with a passing build. I have seen plugins skipped for failing builds.
remove dead code
renamed the PluginStatsRepository to BuildInformationRepository seems more appropriate now
updated to properly handle when the build starts the project list on the session will be initialized to null
removed the "passed" column from the build table since we are only storing passing builds now
dropped the "execution_hashcode" from the plugin_execution table this was only needed with the old way of storing data as the build ran