PROCESSING_COST_MIN_THREADS can get ignored by scan fragment.

There is a bug in PlanFragment.java where scan fragment might not follow PROCESSING_COST_MIN_THREADS set by user even if total scan ranges allow to do so.

Frontend planner also need to sanity check such that PROCESSING_COST_MIN_THREADS <= MAX_FRAGMENT_INSTANCES_PER_NODE.