Inline constraints

This one contains all the remaining constraints except the Regex constraint which is not registered to work as inline constraint. I will add it as a separate commit/PR, it needs special handling as it depends on the behavior of not splitting the parameters on a comma. ( The code we had would not work as today we have two constructors for RegexConstraint)..More on this in the PR.
@harshgMSFT @Eilon @yishaigalatzer 

For all of these integer-like constraints, I don't see much value in doing the `is long` check before converting to string and then back to `long`. The `is` will only succeed if the value is in fact a boxed long (`int`, `double`, et al will fail this test). 

It seems unlikely to me that anyone has ever written any code (other than us) that exercises this branch, so why have it? The convert-to-string-parse-as-long technique is still correct for boxed longs.

Am I missing something here?