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)
I'm not sure that adding this as an argument to create_collection is the way to go, though.  @athanatos what do you think?

Also, unfortunately the Transaction encoding is not structured such that non-understood ops can be ignored, so some care has to be taken when adding new ops or op arguments.  Probably need to use the OSDMap get_up_osd_features() bits or something.