Make the demo console state label honest about live health

[codeforester]

Goal

Make the demo console's service-catalog status copy honest about what it
actually knows.

Background

services/demo-console/src/App.jsx derives required, optional, and
cataloged from static service-catalog metadata. The catalog is fetched once
from /service-catalog.json; no service health probes or runtime status
updates are performed. The current State label can therefore be read as
live health even when a service is down.

Scope

• Use the no-probe path: rename the column and supporting copy to describe
  catalog role/requirement rather than live health.
• Keep the existing static values (required, optional, cataloged) unless
  a clearer equivalent is needed for the rendered label.
• Update representative-environment documentation and component tests so the
  semantics agree.
• Keep live health polling, stale timestamps, and service probes out of this
  change; those would be a separate product decision.

Acceptance Criteria

• The rendered column/value vocabulary clearly describes catalog
  requirement or scope and cannot reasonably be read as live health.
• The UI copy and representative-environment documentation agree on the
  static catalog semantics.
• Tests cover the chosen semantics, including a service that would be
  unavailable if live health were being checked.
• Existing summary counts and catalog rendering remain unchanged.

Validation

• npm test in services/demo-console
• npm run build in services/demo-console
• bats tests/demo_console_test.bats
• mise run validate

Non-Goals

• Does not add live service-health polling or network probes.
• Does not change the service catalog data model.
• Does not redesign the console or change responsive layout behavior.

Project Fields

• Status: Ready
• Priority: P2
• Area: Product
• Initiative: Adoption Polish
• Size: M
• Milestone: v0.2.0

Agent Assignment

• Assignee: codeforester