CI migration: MG to Integration/Unit Tests

[plebhash]

this table should guide the CI migration away from MG

MG test	migration strategy	comment	issue	migration status
interop-jdc-change-upstream	integration test	will help continue shaping #1122	#1207	#1343 WIP (blocked)
pool-sri-test-reject-auth	removal	motivation for test is not clear MG_reject_auth doesn't make sense > Probably this was a test related to some initial work related to authentication mechanisms which were never really implemented. > I think we should add a proper test in the future, as soon as we will have some kind of auth system in place on the Pool. #1482 (comment)	#1481	#1482 ✅
translation-proxy	integration test	will greatly improve CI experience, MG test is highly undeterministic	#1208	#1262 ✅
interop-jd-translator	integration test		#1353	#1354 WIP
bad-pool-config-test	unit test	this test is asserting internal architecture flow, not message flow between roles	#1305	#1306 ✅
standard-coverage-test	removal	mixing code coverage with MG, not clear why... contribution from devs who are not around anymore	#1350	#1363 ✅
jds-do-not-panic-if-jdc-close-connection	unit test	this test is asserting internal architecture flow, not message flow between roles	#1348	#1360 ✅
jds-receive-solution-while-processing-declared-job	integration test		#1419	blocked by #1420
translation-proxy-broke-pool	integration test	ideally, Sniffer should have a primitive to assert a connection was broken... but that is currently blocked by #1389 so we bypassed that by asserting that a port is free inside the test	#1414	#1415
translation-proxy-old-share	potential removal	requires further investigation, we're not sure if "outdated" job_id is a sufficient criteria for rejecting shares additionally, this test could potentially require a way to intercept/replace Sv1 messages (Sv1 Sniffer?), which could be a substantial engineering effort so for now, I'd postpone (and potentially discard) this migration
interop-proxy-with-multi-ups-extended	?
interop-proxy-with-multi-ups	?
jds-do-not-fail-on-wrong-tsdatasucc	?
jds-do-not-stackoverflow-when-no-token
jds-setupconnection-with-async-support	?	the async flag of SetupConnection is being replaced via stratum-mining/sv2-spec#121, so this test should change strategy
jds-setupconnection-without-async-support	?	the async flag of SetupConnection is being replaced via stratum-mining/sv2-spec#121, so this test should change strategy
pool-sri-test-1-standard
pool-sri-test-close-channel	potential removal	test motivation is not clear do we even want tProxy to shutdown just because pool closed a channel?
pool-sri-test-extended_0		#1474
pool-sri-test-extended_1		#1475
sv1-test		Sv1 Sniffer required?

---

Aside from the MG tests listed above, #1077 should also be completed within the context of this effort.