Loading a plugin should also generate a synthetic transaction

[sporkmonger]

Currently, a plugin that's compiled for an incompatible version of the SDK or that has some other issue may not produce an error at plugin load time. These errors might only occur once the application begins serving requests. Triggering a synthetic transaction and potentially allowing the program to exit immediately with an error could help prevent bad deploys from going to production.

[sporkmonger]

Alternatively, maybe this should happen in a subcommand, something like bulwark-cli check and that could be run at startup before the server command?