fix(st2client): fix TypeError when displaying help for actions with mixed parameter position types

[balgaly]

Summary

Fixes #5130 — st2 run pack.action -h crashes with TypeError: '<' not supported between instances of 'str' and 'int' when the action has some parameters with a numeric position attribute and others without.

Root cause

_get_parameter_sort_value returns either int(position) or str(name) depending on whether the parameter has a position attribute. Python 3 does not support < comparisons between int and str, so sorted() raises a TypeError when it tries to compare parameters of both kinds.

Fix

Replace the flat return value with a 3-tuple (tier, int_pos, name):

• Parameters with a position attribute return (0, int(position), "") -- sorted by position first.
• Parameters without a position attribute return (1, 0, name) -- sorted alphabetically after positioned ones.

Tuples are compared element-by-element. Because the first element always differs between the two groups (0 vs 1), Python never attempts to compare an int against a str.

Test

Reproducer (from the issue):

st2 run librenms.get_bgp_sessions -h
# was: ERROR: Unable to print help for action "librenms.get_bgp_sessions". '<' not supported between instances of 'str' and 'int'
# now: displays help correctly

The fix is additive -- any action whose parameters all have position attributes or all lack them continues to sort identically.

[CLAassistant]

All committers have signed the CLA.

[balgaly]

I pushed a follow-up commit adding unit tests for _sort_parameters and _get_parameter_sort_value to st2client/tests/unit/test_command_actionrun.py. Three cases are covered: mixed positioned/unpositioned parameters (the regression case from #5130), all parameters with a position, and all parameters without.

On the CI failures: the Integration Tests (Orquesta) - Python 3.10 job failed, but the same test passed for Python 3.8, 3.9, and 3.11. The change here is a client-side sort key with no server-side effect, so it cannot influence Orquesta workflow execution. Cross-referencing against PR #6372, the base branch has had intermittent CI instability for some time. The failure looks pre-existing rather than anything introduced by this PR.

[balgaly]

Just pushed a follow-up to fix the remaining CI failures:

• Flake8 E241 — removed extra alignment spaces after : in the test dict literals (lines 414/417 of test_command_actionrun.py)
• CHANGELOG.rst — added an entry under in development as required

All CI checks should pass now. Happy to make any other changes.

[balgaly]

Pinging to clarify the CI status shown on this PR. The checks listed as failing are from earlier commits. The latest run (April 11) passed all jobs: https://github.com/StackStorm/st2/actions/runs/24292372407

Happy to address any review feedback.

[balgaly]

Looking at the failure logs more closely: all failures are infrastructure-level pants build errors ("Building pytest.pex failed with exit code 1", "Building build_backend.pex failed") with artifact upload conflicts (409 Conflict). These are CI runner issues unrelated to the code change. The unit tests and lint checks all passed in the parallel runs. Happy to rebase against master if that helps trigger a clean run.