First draft of upg tests, ignore PR failures

[vipbhardwaj]

UPfrade test for SGW.
Currently ignore the failures on focus on how can I handle the code for SGW version switch. I need help with the specific code inside the file ./jenkins/pipelines/QE/upg-sgw/test.sh.

Also I changes the pre-commit-config since it wasn't allowing me to commit code with language as unsupported.

[borrrden]

I really still think this test is trying to do way more than it needs to. If the tests were focused on just sg upgrade they could be so much faster if written in another framework.

[vipbhardwaj]

There's no change related to your subcomments, but the team and I have decided that this can be kept for a simple upgrade test run quick and basic (~30 min), especially for verification of <= 4.0.0 this is enough.
However, you were right about the fact that a new framework should be devised, as the team has decided too that > 4.0 has significant new features like mixed version mode supporting rolling upgrades that probably the TDK alone cannot test. Hence that is under doing my homework and learning about 4.1.x so as to decide what would be the foundation of the testing there and hence the new framework too.

For now

This PR can be merged to main but I would like to discussed with you as to how you designed and made TDK evolve to where it is now since the infrastructure part of the new-framework is not gonna be just SGW related or UPGRADE testing related.
Requesting your approval on this.

[borrrden]

For my sanity I will stop commenting on things besides what is changing in the TDK since this is purely in the SGW realm. The changes here are small, and the only weird part is that the orchestrator has sort of "opt out" flags for start while it has "opt in" optional flags for stop.