fix: assert is not necessary when the table config is updated

[foreverneverer]

Related-Issue

apache/incubator-pegasus#903.

Change

c++ client will crush for assert if server table config is changed, for example, remove table and re-build same name table.
But it's not necessary because config-update will trigger the client fetch latest right config, which don't has any problem.

I found the problem is that the duplication module use the c++ client code: if one duplication failed, I want drop the remote table and re-start new duplication task, but it will result that all the master replica crush for the remote table config changing

So please must merge this pr when release duplication(apache/incubator-pegasus#892)

[acelyc111]

If the duplication is in progress, then drop the dest table and create a new one, how will the duplication act now? restart the duplication or keep in progress?

[foreverneverer]

If the duplication is in progress, then drop the dest table and create a new one, how will the duplication act now? restart the duplication or keep in progress?

• In DS_LOG, it will keep sending plog
• In DS_APP , it will failed(before the pr, it will crush) and you have to remove the duplication and re-create new duplication
• In DS_START, if remote-cluster has exist same name table, it will block and report exist error, and auto-create new one after you drop it