Provide user feedback when tables run against columns that are null/missing

[dogversioning]

Part of the spirit of the v2 refactor is to make sure that you can do a partial library run and upload it - this will have some limited diagnostic/clinical value - but we should also inform a user about these states so that, if something is strange about their data, they have enough information to debug it.

We should do something like one or more of the following:

• Log to the command line tables where we had to null cast an entire column
• Log to the command line tables where we had to create an empty version of the table
• Point users elsewhere (metrics?) for more details info
• Create a markdown/html/pdf describing the issue in more detail