tutor status support from MFEs

[e0d]

Is your feature request related to a problem? Please describe.

A useful approach for MFE development with Tutor is to

1. Enable the MFE plugin
2. Bind mount 1 or more MFEs
3. Shut down specific MFEs, e.g. tutor dev stop learner-dashboard
4. Use npm to start a dev server npm run dev

It would be useful for tutor status to provide some better visibility here.

Currently if you run

tutor dev status you get output like the following

tutor_main_dev-mfe-1             
docker.io/overhangio/openedx-mfe:19.0.0-main-indigo    "caddy run --config …"   
mfe             19 minutes ago   Up 19 minutes   
80/tcp, 443/tcp, 2019/tcp, 443/udp, 
0.0.0.0:1984->8002/tcp, 
0.0.0.0:1990->8002/tcp, 
0.0.0.0:1993->8002/tcp, 
0.0.0.0:1994->8002/tcp, 
0.0.0.0:1995->8002/tcp, 
0.0.0.0:1997->8002/tcp, 
0.0.0.0:1999->8002/tcp, 
0.0.0.0:2000->8002/tcp, 
0.0.0.0:2001->8002/tcp, 
0.0.0.0:2002->8002/tcp, 
[::]:1984->8002/tcp, 
[::]:1990->8002/tcp, 
[::]:1993->8002/tcp, 
[::]:1994->8002/tcp, 
[::]:1995->8002/tcp, 
[::]:1997->8002/tcp, 
[::]:1999->8002/tcp, 
[::]:2000->8002/tcp, 
[::]:2001->8002/tcp, 
[::]:2002->8002/tcp

While you can determine from that with inside knowledge that port 1996 isn't being proxied and thus the learner-dashboard isn't running, it would be nicer to get a status for MFEs that is similar to what you get for backend services.