Add support for additional data constraints beyond type checking in the IR

[AttilaMihaly]

Many business use cases include extra data constraints beyond what Morphir's current type system can provide such as natural number, positive integer, 3 character string, ...

There are some programming languages that provide the ability to constrain values further such as Microsoft's Bosque Language. We would like to incorporate some ideas from there to improve the verification capabilities of the platform.

[AttilaMihaly]

As we are looking at various technologies used for domain modeling a core set of data constraints is starting to emerge. It looks like the majority of real-world use-cases can be covered with the following set of data constraints on simple types:

• String
  • min/max/exact length
    • having this constraint allows us to map the type more accurately to certain backends such as relational databases
  • regex
• Integer
  • min/max value
    • these constraints would allow us to:
      • calculate the number of bytes needed for storage and the most efficient type mapping in the backend language (short, long, ...)
      • represent data quality checks like an amount that should be positive or that it shouldn't exceed a certain value (fat-finger check)
• Decimal
  • min/max value
    • see above
  • precision (decimal places)
    • using a specific precision is a frequent use-case especially in financial calculations
    • having a precision allows us to map the type more accurately to certain backends such as relational databases
    • having precision on a decimal brings in some questions around rounding but those will only come up when operators are applied so we will not cover those here
• ? Float
  • byte length
  • this feels a bit too technology specific currently to represent