Improve bytes, gb, and mb angular filters

[Matthew D. Wood]

In the horizon/static/horizon/js/angular/filters/filters.js file, there's 3 filters that deal with disk-sizings: bytes, gb, and mb.

The bytes filter should likely accept a "target unit" input parameter and lock all output to that unit instead of auto-determining the unit.

We should also probably complete the whole set of kb, mb, gb, tb, pb.

Also, the existing gb and mb filters are pretty naive and simplistic. They should likely do more than just check for numbers and append "MB" or "GB" to the value. Candidate improvements include:

    A) Checking for a string that is already of the correct format
    B) ???

[Matthew D. Wood (woodm1979)]

Completed the whole set of filters kb, mb, gb, tb, and pb.

[Matthew D. Wood (woodm1979)]

Checking for a string that is already of the correct format may require a rewrite of sorts. Because of gettext reasons, we can't really slice the input string intelligently, nor slice the interpolate string. If we didn't need to use gettext this would be easy.

... or maybe there's another way entirely?

[Matthew D. Wood (woodm1979)]

bytes now accepts a label.

Maintained 100% test coverage in all patch-sets!

[Matthew D. Wood (woodm1979)]

After some discussion with Thai and Travis, we're going to add a "toBytes" filter which will down-convert things to bytes, which will allow this type of chained filter:

input_value | toBytes:MB | bytes # convert from MB into a more appropriate unit.
or
input_value | toBytes:MB | bytes:GB # convert from MB to GB

I'm going to see if I can't make this into a single filter, but the syntax may be a bit confusing.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Matthew D. Wood (<email address hidden>) on branch: master
Review: https://review.openstack.org/177572