Use the commit that actually landed in upstream spack

[tmadlener]

BEGINRELEASENOTES

• Use the spack that landed in upstream spack for py-onnx. This has the better matching criteria for when it should be applied.

ENDRELEASENOTES

After just spending about half an hour wondering why the patch that I wanted seems to not have been applied.

[jmcarcell]

I'm actually not sure what to do in the rare cases where the cherry pick and what actually lands in spack differ significantly. Since the build was done with the original cherry pick I think for building with the Key4hep builds on cvmfs as an upstream the builds it is better to keep the original one, otherwise if there is any difference that changes the hash of the package rebuilds will be triggered. But if the original is kept then it's an issue for people that are building.

I'm going to close this for now since I'm going to update all the cherry picks for the nightlies that have been deployed today soon anyway.