Remove unnecessary use of minValue and maxValue in the ProgressBar

[matuzalemsteles]

In the API, it no longer uses minValue and maxValue.

[jbalsas]

Hey @matuzalemsteles, why are those no longer necessary? How does the component work now?

[matuzalemsteles]

hey @jbalsas, it no longer has the possibility of being able to choose the value of minValue and maxValue the logic is in Soy, just pass the value. This was corresponding to this PR deprecate/metal-clay-components#252 e82590f#diff-685086abd487edf3c96e4f84a1af38ba

[julien]

@jbalsas, @matuzalemsteles if I remember correctly the minValue would always be 0 and maxValue would always be 100. This is something we saw with @carloslancha and UX.