docs: drop redundant hyphens from -ly adverb + adjective/participle compounds

Fixes 22 of 23 Microsoft.Hyphens hits: an adverb ending in -ly doesn't
need a hyphen to the word it modifies (minimally scoped, currently
running, deliberately stopped, ...) -- the -ly ending already
unambiguously signals it's modifying the following word, so the
hyphen is redundant per Microsoft style.

Left one hit alone: docs/web-ui/dashboard.md's 'checked-not-originally-
active' is a single 4-word compound designator (parallel structure
with 'unchecked-was-active' right before it in the same sentence,
describing a diffing algorithm's two possible states), not an
ordinary -ly-adverb modifier -- dropping just the one hyphen vale
flagged would have broken the compound into a dangling
'checked-not-originally active' fragment. Also rewrote
docs/scheduler/coordinator.md's 'still-fully-queued' as a predicate
('DAGs that are still fully queued') rather than leaving a similar
broken partial-hyphen chain, since 'still' and 'fully' are both plain
adverbs with no reason to hyphenate at all once dehyphenated
consistently.

Verified via vale: only the one deliberately-left hit remains.

docs/scheduler/jobq.md

@@ -18,7 +18,7 @@ Two ideas are all there is to it:
   a big operation is really a short, ordered sequence — not a single
   black box that's either "done" or "not done."
 - **A step can need a shared resource**, which only so many steps can hold
-  at once (a "slot"). If every currently-running step already holds the
+  at once (a "slot"). If every currently running step already holds the
   slots it needs, a new step that wants the same one waits its turn —
   that's the whole reason things queue instead of all firing at once.