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.
Historically in MVC/Routing data that is in the URL (path + query string) is considered invariant culture, and data in the body is considered current culture. Why, you ask? Because we said so :smile: Part of the reason is that URLs are copy-pasteable, linkable, and shareable, and you don't generally want those to be dependent on the user's culture (e.g. I send you a URL and you can't access it just because of some browser setting). However HTTP bodies are submitted directly by the user.

Yeah, it's somewhat arbitrary. I'm sure it's worth revisiting in some general sense, but for here it's invariant culture.