on new tenant model creation migrate private schema rather than load schema.rb

This solves the problem (#7) where the private schema schema_migrations table does not contain the complete set of migration versions after creating a new tenant model.