Support 'expected_num_objects' parameter when creating pool for pg folder splitting

This patch adds a new parameter for pool creation named 'expected_num_objects', to give user a choice to specify the number of objects he/she would like to put into the pool. This information is used to pre-hash PG's namespace by creating a certain number of folders, so as to avoid run-time folder splitting which could saturate disk I/O.

Testing - test against various combinations of PG number and splittings.

Issue - as we add two new fields to coll_t struct, and given its encode/decode logic, when we bump up the version number, it could break old version software. This would request to upgrade all nodes before creating new pool.

Todo - doc the behavior.

Signed-off-by: Guang Yang (yguang@yahoo-inc.com)
If we want to support dynamically adjusting the value of the field and splitting, I think it makes sense to add a new operation. And as the use case we want to support is to let user specify a rough number at pool creation time so that we pre-split to the right amount of folders needed to avoid runtime splitting, adding it to the collection creation operation is the easiest way I found to achieve such purpose (without any side effect):)