Fixing the issue #123

Here is what the fix does:
1. If the parameter has inline constraint but is optional as well, it creates OptionalRouteConstraint -- which is new type of constraints added -- for that parameter. The OptionalRouteConstraint takes the original IRouteConstraint that would have been created for this parameter as input.

2. The 'Match' method on OptionalRouteConstraint checks if the value for the parameter is present. If it is it delegates to the 'Match' method of the original IRouteConstraint. If the value is not present, it returns true. 
would be good to see the same test where you call `builder.AddResolvedConstraint("id", "int")` and **then** `builder.SetOptional("id")` to verify that the order of the calls is not important