mon/OSDMonitor: Only set erasure-code-profile for erasure pool when
creating a pool.

After creating a replicated pool, we can't remove the default
erasure-code-profile. For example:
root@test:/etc/ceph# ceph osd pool create test 2 2
pool 'test' created
root@:/etc/ceph# ceph osd erasure-code-profile rm default
Error EBUSY: test pool(s) are using the erasure code profile 'default'

This is because when creating a pool the code don't check the pool type
and set the erasure-code-profile=default to all replicated pool.
Also in OSDMonitor::erasure_code_profile_in_use, it don't check pool
type and only check the erasure-code-profile. So bug occur.

Signed-off-by: Ma Jianpeng <jianpeng.ma@intel.com>