Deprecation of factory functions using Result

[LVMVRQUXL]

Description

Like discussed in #315, we would like to deprecate the factory functions using the Result type with a warning level.
The deprecation notices should suggest to use the public constructor of the target type instead, and should indicate that these warnings will be errors in the next minor release (see issue #265).

Finally, we should update the documentation about our design goals on error handling by explaining how we manage possible errors instead of using the Result type.

Dependencies

This issue is blocked by the following ones:

• Stabilization of factory functions named create* for stable types #321

Checklist

• Deprecate the factory functions, refactor code, update the Unreleased section in changelog and check the generated documentation for the following types:
  • NegativeInt
  • NonZeroInt
  • PositiveInt
  • StrictlyNegativeInt
  • StrictlyPositiveDouble
  • StrictlyPositiveInt
  • NotBlankString
  • NotEmptyList
  • NotEmptyMap
  • NotEmptySet
• Update our design goals on error handling.

[LVMVRQUXL]

We should split this issue by type.

[LVMVRQUXL]

The discussion #315 and its related issues will not be implemented.

[LVMVRQUXL]

We will integrate this issue in the idea #335, but we should split this issue by type for more granularity.

[LVMVRQUXL]

This have been separated by types. See the topic #587.