Drop the Actions tab, and give wide panels the width instead of a scrollbar

Four changes from looking at the built page.

ACTIONS HELD ONE CARD. Tracked services was the only thing in it, and it was
the wrong split anyway: a service row reads as state first and a Start/Stop
second, so separating the buttons from the state they act on made a tab that
answered no question on its own. Services move to Metrics, beside the rest of
what the endpoint reports, and the group is gone from the contract.

WIDE PANELS SPAN, THEY DO NOT SCROLL. Network interfaces carries adapter,
address, MAC, speed and state; at half page width in the two-column flow it
either squeezed every cell to three lines or offered a horizontal scrollbar.
A scrollbar for data that just needs room is a layout failure. Table panels
now take column-span, which is the multi-column layout's own answer, so short
fact cards stay two-up around them. The wrapper keeps overflow-x only as a
floor for a genuinely narrow viewport.

SOFTWARE AND ACTIVITY RUN FULL WIDTH. Both are single long lists, and a list
split into two balanced columns reads as two unrelated lists with no way to
tell where the first ended. Details and Metrics keep the two-column flow
because they are short cards, which is what that flow is good at.

Contract 0.29.0 keeps its number: it is unreleased, and the group vocabulary
it introduces has simply lost one value before anybody could depend on it.

Scope: product

shopdb/core/api/pluginui.py

@@ -25,7 +25,7 @@ pluginui_bp = Blueprint('pluginui', __name__)
 #
 # 'details' is first and is the fallback: it holds what an asset IS, which is
 # what a panel declaring nothing almost always contributes.
-ASSET_PANEL_GROUPS = ('details', 'software', 'metrics', 'actions', 'activity')
+ASSET_PANEL_GROUPS = ('details', 'software', 'metrics', 'activity')
 
 
 def _collect(hookname):

shopdb/plugins/base.py

@@ -372,8 +372,7 @@ class BasePlugin(ABC):
             'position':   int,        # order among panels
             'group':      str,        # OPTIONAL. Which tab on the detail page:
                                       # 'details' | 'software' | 'metrics'
-                                      # | 'actions' | 'activity'. Omitted means
-                                      # 'details'.
+                                      # | 'activity'. Omitted means 'details'.
         }
 
         ON 'group'. The detail pages are tabbed, and a panel says which tab it
@@ -384,8 +383,14 @@ class BasePlugin(ABC):
         existing plugin working untouched: an unknown or absent group resolves
         to 'details', which is the tab that holds what an asset IS. Reach for
         another group only when the panel is the thing that tab exists for -
-        an inventory listing, live telemetry, controls that act on the machine,
-        or a history feed.
+        an inventory listing, live telemetry, or a history feed.
+
+        There is deliberately no group for controls. A panel that acts on the
+        machine belongs beside the state it acts on: tracked services read as
+        telemetry first and a Start/Stop second, so they live in 'metrics' with
+        the rest of what the endpoint reports. Splitting the buttons away from
+        the state they change made a tab that held one card and answered no
+        question on its own.
 
         Consumed by GET /api/pluginui/asset-panels?assetid=<id>, which returns
         the panels matching that asset's type. Disabled plugins