requesting additional support for mjpegPort (mp) also along with wdaPort(p) for cmd: tidevice wdaProxy

tidevice -u $UDID wdaproxy -B RDSRunner.xctrunner -p 8100 -mp 9100

###add to main file
p = None
m = None
if args.port:
cmds = [
sys.executable, '-m', 'tidevice', '-u', d.udid, 'relay',
str(args.port), '8100'
]
p = subprocess.Popen(cmds, stdout=sys.stdout, stderr=sys.stderr)
if args.mjpegport:
cmds = [
sys.executable, '-m', 'tidevice', '-u', d.udid, 'relay',
str(args.mjpegport), '9100'
]
m = subprocess.Popen(cmds, stdout=sys.stdout, stderr=sys.stderr)

###add to main file

if args.port:
cmds = [
sys.executable, '-m', 'tidevice', '-u', d.udid, 'relay',
str(args.port), '8100'
]
p = subprocess.Popen(cmds, stdout=sys.stdout, stderr=sys.stderr)
if args.mjpegport:
cmds = [
sys.executable, '-m', 'tidevice', '-u', d.udid, 'relay',
str(args.mjpegport), '9100'
]
m = subprocess.Popen(cmds, stdout=sys.stdout, stderr=sys.stderr)

Start at the tidevice wdaProxy CLI entry point and reproduce the command with -p 8100 and -mp 9100. Trace how the existing wdaPort option is handled, then verify that both requested local ports relay to 8100 and 9100 when the command runs.

Written by the indexing model from the issue text.