mvn deploydb only creates 4.0 DB, not 4.1

In 4.1 branch and on developer environment, if we run mvn -P developer -pl developer -Ddeploydb to deploy fresh db, it will create 4.1 CS DB, which will only run 4.0 CS schema. Only when we start MS, it will upgrade DB to 4.0, this is not designed behavior for 4.1 DB change. The correct behavior is that mvn deploydb should create a fresh 4.1 DB, then in next release we can move DB upgrade logic from MS start code. The commit for this is already in master, we just need to cherry-pick the following two commits from master to 4.1: 5b760f903f1a3145f62d05c1d3c142b710248026 and a32c6d5c9d50320b2526bc9e8a6820dd1e0987f0.