Implement optional min and max values for numeric types

## Background
Having optional minimal and maximal value boundaries for numeric types will allow stricter control of standardization of these types.

## Feature
Optional metadata of keys `min` and `max` (_long integer_ or _double_ in _string_ format, adhering to pattern if that has been specified), that will limit the smallest and largest number allowed in field.
If the boundary is breached the fields default value will be used (or the global one if field doesn’t have a explicit one). Please not, that the default value **can** be outside the boundaries defined by `min` and `max`.

## Validations
* must be a number in _string_ format (_long_ for integral types, _double_ for fractional ones) - _error_
* adhere to pattern - _error_
* if out of the type limits - _warning_
* if both `min` and `max` defined and `max` < `min` - _warning_