feat: add limits to input attributes

[kdrienCG]

This PR adds the possibility to specify a min and/or a max value to Wrappers attributes.

registerWrapper( viewKeysStruct::fooString(), &m_foo )
  .setLimits( 0.0, 1.0 )  // sets a minimal value of 0.0 and a maximal value of 1.0

This will serve as a documentation for values, but also prevents users from making typos that could lead to wrong results, taking time to find (if noticed).

The limits come with 3 modes:

• Indicative: No validation of the input is made, serves as documentation only.
• Warning: A warning is emitted if the attribute's value is outside the allowed range.
• Error: An error is emitted if the attribute's value is outside the allowed range.

The mode can be set when specifying the limit, using this syntax:

  .setLimits( 0.0, 1.0, LimitsMode::Warning )

... or it will default to Warning if unset.

Limits also support inclusive and exclusive bounds:

  .setLimits( inclusive( 0.0 ), exclusive( 1.0 ) )

Not using inclusive(...) or exclusive(...) will default to an inclusive limit.

---

Some examples:

  .setLimits( 0.0, 1.0 )  // [0.0, 1.0]
  .setLimits( 0.0, std::nullopt )  // [0.0, +inf)
  .setLimits( inclusive( 0.0 ), std::nullopt )  // [0.0, +inf)
  .setLimits( std::nullopt, exclusive( 0.0 ) )  // (-inf, 0.0)

[dkachuma]

I really like this idea. It will simplify greatly some of the boiler plate validation code.

Will this work for lists of numbers?

[dkachuma]

I would add the range to the message.

Also will this show the full context, not just the field name? Should we use getDataContext()?

[dkachuma]

Suggested change

	LimitsMode mode = LimitsMode::Warning )
	LimitsMode mode = LimitsMode::Error )

I think error is a better default here (most cases would be errors).