[Persistent subscription] figure out why same host/container cannot work in this capacity scenario.

[yunhanw-google]

Agree, maybe normal python test could achieve this including the device reboot scenario as well, but during testing, we find If using the two controller (devCtrl and devCtrl2) in one same container/host to execute this test, the accessory can still resolve the address for first controller even if the first controller is shutdown by 'self.devCtrl.Shutdown()'. And the server will fail to establish the subscriptions immediately, which makes it hard to send the new subscription request from the second controller, which may be the bug.

We have added the multiple mobile container to work around it, cirque provide the multiple container management here, so we use cirque for this testing. We would like to add this test to gate the persistent subscription quality issue fixed by #30491 asap for future glitch.

After ICD work completes, we would try to explore and figure out why same host/container cannot work in this test scenario.