Handle alter events when replicate to cluster with hive.strict.managed.tables enabled.

Some of the events from Hive2 may cause conflicts in Hive3 (hive.strict.managed.tables=true) when applied. So, need to handle them properly.
1. Alter table to convert non-acid to acid.

• Do not allow this conversion on source of replication if strict.managed is false.

2. Alter table or partition that changes the location.

• For managed tables at source, the table location shouldn't be changed for the given non-partitioned table and partition location shouldn't be changed for partitioned table as alter event doesn't capture the new files list. So, it may cause data inconsistsency. So, if database is enabled for replication at source, then alter location on managed tables should be blocked.
• For external partitioned tables, if location is changed at source, the the location should be changed for the table and any partitions which reside within the table location, but not for the partitions which are not within the table location. (may be we just need the test).