Implementation of boundary annotations should allow for none

[GideonKoenig]

Is your feature request related to a problem?

Currently a parameter that has a boundary annotation set, does not allow none as value. Sometimes there are valid intervals specified for parameters that could be used.

Desired solution

In the Interface there should be a checkbox that can be checked, to signal, that none is allowed.
In the automatic generation, you can check, if the type contains none which would imply, that none should be allowed.
In the implementation of the boundary annotation wrapper, these changes need to be implemented as well.

This issue is kind of similar to Safe-DS/Library-Analyzer#36

Possible alternatives (optional)

Just don't automatically set boundary annotations for parameters that allow none as value.

Screenshots (optional)

No response

Additional Context (optional)

No response

[GideonKoenig]

Maybe it would make more sense, to change the implementation of the boundary annotation, to check if the provided value is of the type that the boundary is associated with (Integer or float).
This way boundary annotations could be easily set even as part of broader sets of allowed types or be stacked on top of each other (for different types - see Safe-DS/Library-Analyzer#36).

[GideonKoenig]

This issue will be solved by Safe-DS/Library-Analyzer#36 and is now redundant.