fix: handle non-numeric input for multiple-choice parameters in set_new_value

The is_multiple_choice branch in set_new_value called float(s) with
no try/except block. Both the is_bitmask and numeric branches properly
catch ValueError and raise user-friendly translated error messages.

If a user types a non-numeric string for a multiple-choice parameter
(e.g. the choice label 'Disabled' instead of its numeric key '0'),
the raw Python error 'could not convert string to float' was raised
instead of a friendly translated message.

Fixed by wrapping float(s) in a try/except ValueError matching the
pattern already used in the bitmask and numeric branches.

Add two regression tests covering the non-numeric error case and
the valid numeric input case.

Author: prajakta128

ardupilot_methodic_configurator/data_model_ardupilot_parameter.py

@@ -372,9 +372,7 @@ def set_new_value(self, value: str, ignore_out_of_range: bool = False) -> float:
             try:
                 new_value = float(s)
             except ValueError as exc:
-                raise ValueError(
-                    _("The value for {param_name} must be a number.").format(param_name=self._name)
-                ) from exc
+                raise ValueError(_("The value for {param_name} must be a number.").format(param_name=self._name)) from exc
             # No change
             if new_value == self._new_value:
                 raise ParameterUnchangedError(

tests/test_data_model_ardupilot_parameter.py

@@ -1155,6 +1155,8 @@ def test_set_fc_value_maintains_comparison_state() -> None:
 
     # Assert: No longer different
     assert param.is_different_from_fc is False
+
+
 def test_set_new_value_multiple_choice_non_numeric_raises_friendly_error(param_fixture) -> None:
     """
     Bug fix: non-numeric input for a multiple-choice parameter raises a friendly ValueError.