chore: bump Pytorch version to 2.2.1 in tests

[SdgJlbl]

Fixes CI following Python 3.12 support.

[thbcmlowk]

Thanks for fixing this! How can we make sure we spot this earlier next time?

[SdgJlbl]

Thanks for fixing this! How can we make sure we spot this earlier next time?

I'm actually not sure 🤔

The end-to-end tests were running fine, so I'm not sure... I guess that the matrices used are not exactly the same between the nightly and the manually triggered end-to-end tests, might be worth looking into it more deeply.

[thbcmlowk]

Thanks for fixing this! How can we make sure we spot this earlier next time?

I'm actually not sure 🤔

The end-to-end tests were running fine, so I'm not sure... I guess that the matrices used are not exactly the same between the nightly and the manually triggered end-to-end tests, might be worth looking into it more deeply.

Yes indeed, I think the local tests are actually never triggered except in the nightly. Can you create a follow-up task so we can look at it later? Thank you!

[thbcmlowk]

/e2e --tests=sdk

[Owlfred]

End to end tests: ❌ FAILURE

Jobs status:

• Camelyon: ⏭️
• Dispatch Jobs: ✔️
• Documentation: ⏭️
• MNIST: ⏭️
• SubstraFL: ⏭️
• SubstraSDK / sdk: ❌

“Rien ne sert de courir ; il faut partir à point.” ― Jean de La Fontaine (Le Lièvre et la Tortue)

[thbcmlowk]

/e2e --tests=sdk

[Owlfred]

End to end tests: ✔️ SUCCESS