feat(ValidationRules): add number validation rules

[CuddleBunny]

Add common validation rules for numeric properties.

resolves #440

[CLAassistant]

All committers have signed the CLA.

[CuddleBunny]

I am unsure about a proper validation message for range. I wish English had a word that meant the same as "between, inclusive." I suspect this is probably okay though because a custom message can be used when this doesn't suffice.

[bigopon]

@CuddleBunny Nice. Maybe it will cause a big confusion without clear documentation, can you help add something too. Also about that, should there be rangeInclusive, rangeBetween?
cc @fkleuver @EisenbergEffect

[CuddleBunny]

@bigopon I can update the documentation, it has moved outside to aurelia/documentation right?

Splitting range into two rules is also a good idea. Perhaps just range and between?

[EisenbergEffect]

@CuddleBunny Yes indeed. Docs are now here: https://github.com/aurelia/documentation/blob/master/current/en-us/7.%20plugins/3.%20validation.md Ping me on the docs PR and we'll get these things in together.

[bigopon]

#518 should go before this @EisenbergEffect @fkleuver

[EisenbergEffect]

@bigopon I've got #518 in now. Do this and all future PRs now need to target the develop branch?

[bigopon]

I think so ... cc @fkleuver

[ricardograca]

Any reason for the documentation to show these when this Pull Request isn't even merged? I had to look in the source code to make sure I wasn't using those rules incorrectly.

[CuddleBunny]

@EisenbergEffect - are we waiting on anything to merge this so that it matches the docs that have been deployed?

[EisenbergEffect]

Apologies! I must have deployed the docs to update something else and forgot this was in there. We've got the dependency merged, so I'm merging this now. I'll work on getting a release out in the next day or two. As things look at the moment, probably tomorrow (Friday afternoon Pacific).