'Force' option broken for quota update

[Kieran Spear]

This change broke the ability to force quotas below the current in-use value by adding new validation checks:

https://review.openstack.org/#/c/28232/

$ nova quota-update --force --cores 0 132
ERROR (BadRequest): Quota limit must be greater than 1. (HTTP 400) (Request-ID: req-ff0751a9-9e87-443e-9965-a30768f91d9f)

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/117438

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/117438
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=bf5d003af694ea1eb95fceea8c36e961092cb516
Submitter: Jenkins
Branch: master

commit bf5d003af694ea1eb95fceea8c36e961092cb516
Author: Kieran Spear <email address hidden>
Date: Tue Sep 9 15:32:13 2014 +1000

    Fix 'force' parameter for quota-update

    Commit 77b4012a02c6b4827a7a6b112f35deb9ce94c395 added further
    validation on the quota update controller that isn't aware of the
    'force' parameter. This validation also duplicated the existing
    validation that *did* honour 'force'.

    This change merges the two validation methods and ensures that the
    validation is skipped when the 'force' parameter is passed in the
    request.

    Change-Id: I25e3ce857a83cb50789a2a61bb01c796128ff4f8
    Closes-bug: #1362405