Add more checks to prevent misconfiguration on store file tracker

For example, when creating new tables, if the store file tracker is configured to MigrationStoreFileTracker, we should fail the creation and tell users you should not use this store file tracker for a new table.

And when switching the implementation for store file tracker, we should let end users first switch to MigrationStoreFileTracker, and then to the final target store file tracker. If end users configure wrong store file tracker, we should fail the alter table operation.