test: add explicit mock_ask_confirmation call assertions to reset workflow tests

[Copilot]

Tests for upload_parameters_that_require_reset_workflow set up mock_ask_confirmation but never asserted whether it was invoked, leaving the confirmation callback behavior untested and vulnerable to silent regressions.

Changes

• Reset-triggering cases (SID_AXIS 0→non-zero, absent→non-zero): added mock_ask_confirmation.assert_called_once() — these paths hit reset_unsure_params and must prompt the user
• Non-reset cases (SID_AXIS non-zero→non-zero, non-zero→zero): added mock_ask_confirmation.assert_not_called() — no reset path is entered, dialog must not appear
• Error case (upload raises ValueError): added mock_ask_confirmation.assert_not_called() — exception is caught before any reset logic, dialog must not appear

# Reset-triggering test now verifies the prompt fires exactly once
assert reset_happened is True
assert "SID_AXIS" in uploaded_params
mock_ask_confirmation.assert_called_once()   # ← added
mock_show_error.assert_not_called()

# Non-reset test now verifies the prompt is suppressed
assert reset_happened is False
mock_ask_confirmation.assert_not_called()    # ← added
mock_show_error.assert_not_called()

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.