Fixed MinDecimal and MaxDecimal if JSR349 is not enabled

**The Issue**
Currently the validation patterns for MinExclusive and MaxExclusive are one of if JSR349 is not enabled, which makes it hard to use the restrictions and will most likely cause issues if an annotation aware generator will try generate a valid request.

**The Fix**
This PR will add one or substract one from the bound to show the proper value, if the inclusive flag is not set.
(This is the default case, because Java's JDK does not have an inclusive flag with default options)