[Task] Declare the advisor health module

[traviswu-bigstack]

Description

CubeCOS's cluster check framework is gaining an advisor component. It reports whether a node enrolled with the Cube AI Advisor still has its agent running, and can repair it by starting the service — see bigstack-oss/cubecos#1483.

The health view is data-driven from this API, but the API's component list is hardcoded in internal/cubecos/module.go and an unknown component name returns 400. So the component must be declared here, or it never reaches the UI regardless of what cubecos reports.

Expected behavior

• advisor is listed in the clusterSys service in OrderSensitiveServices, marked repairable, and placed last so it does not reorder existing modules — that order is the display order.
• advisor appears in both moduleType enums in api/cube-cos-openapi/docs.yaml. There are two; adding it to one leaves one endpoint accepting the name while the other rejects it.

QA Verification

1. GET /api/v1/datacenters/{dc}/healths/services/clusterSys/modules/advisor returns a result rather than 400.
2. The same for the second endpoint that takes a moduleType.
3. The module reports as repairable, so check_repair offers it.

Output artifacts (Definition of Done)

• Handbook knowledge update — land the durable, team-readable knowledge from this
  work into the bigstack-handbook cubecos kb via /bigstack-core:save-to-handbook
  (Topic / Runbook / Known-issue / ADR as fits).