Fixes #2184.

Range constraints were previously ignored when the parameter type did not
match one of the existing numeric range validation branches. For example, a
boolean parameter could be declared with an integer range constraint.

This change:

• rejects integer range constraints for types other than integers and integer arrays;
• rejects floating-point range constraints for types other than doubles and double arrays;
• validates statically typed parameters that are declared without an initial value;
• validates dynamically typed parameters whenever they acquire or change their concrete type;
• preserves the existing scalar and per-element array range validation behavior.

Testing

• Added coverage for incompatible initialized parameter declarations.
• Added coverage for statically typed declarations without initial values.
• Added coverage for incompatible integer/floating-point range combinations.
• Added coverage for dynamically typed parameters changing to an incompatible type.
• Full test_node suite passed: 48/48 tests, using the equivalent patch with the
  rclcpp version matching the available archived Rolling dependencies.
• git diff --check passed.