Current Behavior

When creating a collection without specifying the replication_factor, the collection inherits the default value set in the production.yaml file, but replicas are not created. The expected number of replicas gets created when specifying the replication_factor in the body of the PUT request.

Steps to Reproduce

1. Deploy a cluster of Qdrant nodes (three in my case)
2. Set the storage.collection.replication_factor to a number greater than one (two or three in my case) in the production.yaml file. Shard number is set by default to the number of replicas, so in this case we have three shards.
3. Create a collection (with either REST API or gRPC) without setting the replication_factor in the body of the request

Expected Behavior

I expect to create a collection with the correct number of replicas of the three shards, instead I get no replicas at all, as if the replication_factor was set to 1.

Context (Environment)

This bug makes the default configuration for the replication factor useless, and requires applications to be aware of the desired number of replicas when creating a collection, which should instead be delegated to the infrastructure level.