Drop monasca and senlin from the schema

[Eandalf-Bigstack]

What type of PR is this?

/kind cleanup

Which issue(s) this PR fixes?

Part of bigstack-oss/cubecos#772, specifically bigstack-oss/cubecos#771 (COS UI > Home > Health page after the OpenStack, InfluxDB and Ceph upgrade).

What this PR does?

Removes two services from the schema that CubeCOS no longer ships, so the API stops describing things that are gone.

monasca — removed from CubeCOS by bigstack-oss/cubecos#672 phase 4. Four places still described it:

where	what it claimed
metrics module group	listed monasca beside telegraf and grafana, so a client rendering that group showed a module the cluster does not have
two module-name enums	GET /v1/modules and the repair endpoint both accepted "monasca" as a valid module name
monasca.debug.enabled	a documented tuning for a service with nothing left to configure

senlin — removed from CubeCOS by d4550c91, back on the yoga train. The schema was only half-updated at the time: senlin came out of the module-name enums but stayed in the businessLogic module list and in a senlin.debug.enabled tuning. That asymmetry is why every generated SDK is already clean while the schema still advertised the service. CubeCOS' own cluster check now reports BusinessLogic as watcher alone.

Schema only — no endpoint, request or response shape changes.

Test results (optional)

1). docs.yaml still parses as YAML after both removals, and grep -c monasca / grep -c senlin return 0.

2). Regenerating the TypeScript SDK from this schema in cube-cos-ui produces:

• for the monasca commit: two JSDoc @type unions and two enum members removed — the exact mirror of what a34418d added for metricsDb
• for the senlin commit: sdk/api.ts byte-for-byte unchanged, which is the evidence that senlin was already absent from the module enums and only the non-generating parts of the schema still mentioned it

3). Regenerating api/docs.json in cube-cos-api from this schema yields zero monasca and zero senlin references. That file is embedded into the binary via api/docs.go's go:embed, so this schema change does reach the shipped artifact.

Companion PRs

This PR is the base for the other two; both pin their submodule at this branch and want re-pinning to the merged SHA before they land.

• cube-cos-api — the Go half: the metric queries and the module list
• cube-cos-ui — the UI half: the health-page labels and the regenerated SDK

🤖 Generated with Claude Code

[SekiXu]

Approving. Both removals are the schema catching up to code that already moved, which is the direction that cannot break a client of a shipped build:

• senlin — already absent from cube-cos-api (git grep -i senlin on jim.lin/fix/drop-monasca returns nothing), and senlin.debug.enabled is already gone from cubecos/develop. So the schema was the stale copy, not the leading edge.
• monasca — matches cube-cos-api#656 and cubecos#1457 exactly: the metrics module group loses monasca and keeps telegraf/grafana, the two module-name enums drop it, and monasca.debug.enabled goes at the same time cubecos#1457 deletes the CONFIG_TUNING_BOOL that registers it.

Worth knowing for the merge: this is a clean fast-forward from develop, so a true ff merge puts develop on 3d9065db — which is what cube-cos-api#656 already pins its submodule at. That order works without a re-pin.