[v1.9.x] ONNX fix node output sort

[waytrue17]

Description

Backport #20326.

Checklist

Essentials

• PR's title starts with a category (e.g. [BUGFIX], [MODEL], [TUTORIAL], [FEATURE], [DOC], etc)
• Changes are complete (i.e. I finished coding on this PR)
• All changes have test coverage
• Code is well-documented

Changes

• Feature1, tests, (and when applicable, API doc)
• Feature2, tests, (and when applicable, API doc)

Comments

• If this change is a backward incompatible change, why must this change be made.
• Interesting edge cases to note here

[mxnet-bot]

Hey @waytrue17 , Thanks for submitting the PR
All tests are already queued to run once. If tests fail, you can trigger one or more tests again with the following commands:

• To trigger all jobs: @mxnet-bot run ci [all]
• To trigger specific jobs: @mxnet-bot run ci [job1, job2]

---

CI supported jobs: [sanity, unix-cpu, edge, centos-cpu, miscellaneous, website, windows-gpu, windows-cpu, unix-gpu, clang, centos-gpu]

---

Note:
Only following 3 categories can trigger CI :PR Author, MXNet Committer, Jenkins Admin.
All CI tests must pass before the PR can be merged.

[Zha0q1]

the pylint warning basically means that len(name) are keep being redefined in each loop iteration. refer to https://stackoverflow.com/questions/25314547/cell-var-from-loop-warning-from-pylint
this is actually what we intended but to make it more formal we can change

def str2int(s):

to

def str2int(s, name):
...

node_output_names = sorted(node_output_names, key=lambda x: str2int(x, name))

[waytrue17]

the pylint warning basically means that len(name) are keep being redefined in each loop iteration. refer to https://stackoverflow.com/questions/25314547/cell-var-from-loop-warning-from-pylint
this is actually what we intended but to make it more formal we can change

def str2int(s):

to

def str2int(s, name):
...

node_output_names = sorted(node_output_names, key=lambda x: str2int(x, name))

Thanks for the heads-up!