Restrict flavor fields input on creation/update.

If flavor properties are invalid, an update message error
is shown, but the flavor get deleted.
The reason is that update flavor is not yet supported so horizon
will delete the flavor and create a new one, failing in the last case.

Fields ram and vcpus need to be >= 1 and eph_gb, swap_mb and disk_gb
>= 0 to create a flavor.

Change-Id: I20d178bad6e4e50c0963acdec72ebedb9bbaba17
Closes-Bug: #1269638
Speed up unit tests without coverage

Previously coverage command is always used even if coverage is
not enabled and this makes unit tests slower.

Change-Id: I4311164ef907fbdc66ac66d4999b25054bc9eebd
Closes-Bug: #1272979
Restrict the length of the project name input

There is an allowed maximum length for project name field, but in
current code, it doesn't check or restrict that from UI side, i.e. user
will be able to type in more than what is allowed. After form
submission, it will fail but there is no clear message telling user what
caused failure.

After adding the code to restrict the max length of the project name
field, user will not be able to input more than what is allowed, thus
this error will be prevented from UI.

Change-Id: I6e61387c1e89e47e16354719870047c6e4760989
Closes-Bug: #1276389
Merge "Restrict the length of the project name input"
Merge "Restrict flavor fields input on creation/update."
Merge "Speed up unit tests without coverage"