[Bug]: Datanode does not prevent API usage when schema is not in sync

[ettec]

Problem encountered

It is possible to load a datanode up with network history that would leave its schema out of sync with the binary, in this scenario the APIs would still be available, which could result in unexpected errors. (note, it will not attempt to process events due to block height check)

In the scenario where database if out of sync with binary, API usage should no longer be permitted. Alternatively, if there was a need to run a datanode as read-only (ie will not process events) to view old data with the latest binary an option could be added to forward migrate the data.