Fix GPU Dashboard

[quasiben]

Closes #8567

In #8399 we removed the GPU Executor which caused an outage in the GPU dashboard. This was due to relyin on the ws.extra['gpu'] being populated by the executor. The dashboard now relies on the system monitor for pulling and updating GPU memory/usage

@jacobtomlinson @charlesbluca Can one of you review ?

• Tests added / passed
• Passes pre-commit run --all-files

[github-actions]

Unit Test Results

See test report for an extended history of previous test failures. This is useful for diagnosing flaky tests.

    29 files  ±0      29 suites  ±0   10h 56m 8s ⏱️ - 25m 53s
 4 058 tests ±0   3 943 ✅  - 5    109 💤 ±0  5 ❌ +4  1 🔥 +1 
54 931 runs  +1  52 520 ✅  - 2  2 405 💤  - 2  5 ❌ +4  1 🔥 +1 

For more details on these failures and errors, see this check.

Results for commit 6ea9470. ± Comparison against base commit e434793.

♻️ This comment has been updated with latest results.

[mrocklin]

@fjetter can I ask your team to take a look at this? (or @jrbourbeau)

[jrbourbeau]

Thanks @quasiben. This LGTM -- here's a screenshot of trying this PR out

There were some seemingly unrelated test failures happening, so I merged main. Will merge this PR once CI finishes

EDIT: Confirmed the failures here are known flaky tests