replace lowest/max double bounds with +/- infinity

[christianrauch]

The double bounds use lowest/max on C++, while the Python implementation uses +/- float('inf').

Align the implementations by replacing lowest/max with +/- infinity.

Original issue discovered by @pum1k in #376 (comment).

Fixes #376 .

[christianrauch]

Note to myself: The change appears in example_python because the C++ parameter file is symlinked to this one.

[christophfroehlich]

kind of duplicate of #169. Have you checked if rqt_reconfigure handles this properly? I remember opening a PR there, but not sure now

[christianrauch]

kind of duplicate of #169. Have you checked if rqt_reconfigure handles this properly? I remember opening a PR there, but not sure now

Do you remember what exactly the problem with rqt_reconfigure was?

When I start the rqt_reconfigure plugin via

QT_QPA_PLATFORM=xcb rqt --standalone rqt_reconfigure.param_plugin.ParamPlugin

and set a value, it is applied and I can retrieve it again via:

ros2 param get /admittance_controller double_no_upper_bound

The slider goes from 0 to inf, so using the slider does not make too much sense. But setting it manually via the text field works as expected.

I get a couple of "The range of this parameter is too large for the slider to handle. Scaling down to fit within 32 bits with factor 2.328306435454494e-10." warnings, but those apply to some integer values.