Allow collector and web to fail fast when required tables for span/stat compatibility versions do not exist

[Xylus]

With the introduction of span/stat v2 tables new configuration options were added to ensure smooth transition from v1 -> v2.
The relevant configuration options are as follows:

Collector - pinpoint-collector.properties

collector.experimental.span.format.compatibility.version=v1|v2|dualWrite
collector.experimental.stat.format.compatibility.version=v1|v2|dualWrite

Web - pinpoint-web.properties

web.experimental.span.format.compatibility.version=v1|v2|compatibilityMode|dualRead
web.experimental.stat.format.compatibility.version=v1|v2|compatibilityMode

As it is currently, if the option is set without having the necessary table (for example setting collector.experimental.span.format.compatibility.version=v2 without actually having the table TraceV2), the error is thrown late during runtime after collector startup. This could be especially undesirable for the collector as it could cause data losses.

It would be better to simply stop the collector from starting up correctly at all, and let developers know about it before traffic starts flowing in.
Current plan is to stop the collector/web from starting up under the following circumstances:

• v1 - Fail if Traces or AgentStat tables are missing
• v2 - Fail if TraceV2 or AgentStatV2 tables are missing
• dualWrite/dualRead/compatibilityMode - Fail if either of the v1, v2 tables is missing.