Scaling of clusterpool default size can cause problems with unexpectedly scaling down the pool

[chrisahl]

Tried to scale a clusterpool from 10 to 8 and for some reason the size got set to 1? I called

cm scale cp aws-4-9-sno-2x -size 8

where the -size was passed instead of --size. In this case we need to throw an error and not default to 1. This can really mess up stuff that depends on the clusterpool for OCP resources. For example, CICD

[chrisahl]

Think I might change the logic to default to zero and on validate if size is zero throw an error

[chrisahl]

Fixed