Add comprehensive internet connectivity and uptime tracking documentation

[Copilot]

This PR adds comprehensive documentation for internet connectivity and uptime tracking across the AC Training Lab facilities and partners. The new documentation provides:

Research and Documentation

Network Infrastructure Information:

• University of Toronto (UofT) WPA2-Enterprise setup and IT contact information
• Donnelly Centre (SDL6) network architecture and system administrator contacts
• Structural Genomics Consortium (SDL3) infrastructure and technical contacts
• Hologram IoT cellular backup connectivity solutions and pricing
• Rogers mobile hotspot services for Canadian backup connectivity

Best Practices and Implementation Guidance:

• Industry standard tools for network uptime monitoring (SolarWinds, PRTG, Zabbix, etc.)
• Laboratory-specific monitoring practices for automated systems
• Key metrics and KPIs for measuring network reliability (uptime %, MTBF, MTTR, packet loss, latency)
• Fault tolerance strategies in industrial automation environments

System Architecture Comparisons:

• Edge computing vs cloud-dependent systems for fault tolerance
• Local backup systems and offline operation capabilities
• Cloud vs on-premises reliability comparison with SLA statistics
• Hybrid architecture best practices for maximum reliability

Implementation for AC Training Lab

The documentation includes specific recommendations for:

• Establishing contacts with facility administrators for collaboration
• Implementing backup connectivity using Hologram IoT and Rogers solutions
• Deploying comprehensive monitoring infrastructure
• Developing hybrid architectures combining cloud and local capabilities

Documentation Integration

• Added new connectivity-uptime-tracking.md document to the main documentation
• Updated the documentation index to include the connectivity guide
• Enhanced the network setup note snippet to reference the new comprehensive guide

This documentation will serve as a foundation for implementing robust connectivity monitoring and backup solutions across all AC Training Lab facilities.

Fixes #441.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[sgbaird]

Response from Jeff Liu (subject line: [rt.ccbr.utoronto.ca #12429] AC-Team: Donnelly Network Uptime/connectivity monitor)

We have an uptime monitor server for our websites, it is physically located at Canadacomputer Cloud in UVic in BC. Since it monitors many web servers in Donnelly Centre, it can also serve for the purpose of monitoring network. Please take a look at monitor page for one lab in url below. It has live results in last 3 hours. If your team is interested in monitoring connections from Internet all the way to a server in your room, you can setup a web server with simple index.html for monitoring purpose.

https://uptime.ccbr.utoronto.ca/status/hugheslab

Noticed that the example linked is based on https://github.com/louislam/uptime-kuma (self-hosted focus). Incidentally, it mentioned "Uptime Robot" in the README as one of the inspirations, and it looks promising. Team and Enterprise Plans have 24-month data retention (otherwise 3 months for free and 12 months for "Solo"). $29/month for Team, 100 monitors which would be plenty.

Running a gradio app locally on some hardware and exposing it to internet via https://www.gradio.app/guides/sharing-your-app (apparently can add authentication, though obviously increases the hurdle compared with hosting on HF) is an option.

[sgbaird]

cc @bonnieking, thought you might be interested in this thread.

Related (since we're already using tailscale):

• FR: built-in uptime/performance monitor into tailscale  tailscale/tailscale#12195
• https://tailscale.com/blog/client-metrics
• https://www.reddit.com/r/BlueIris/comments/14x6cwa/tailscale_and_uptime_monitor/

Is connectivity uptime monitoring for our tailscale devices something we could integrate into https://github.com/AccelerationConsortium/sdl-tailscale-monitoring (private repo)?