Compaction control

Coverage Gap: Compaction control and failures

## Finding
Several questions seek ways to manually start compaction, clean up failed compaction plans, or gauge how long a cluster runs if the compactor is offline. Documentation only covers automated scheduling, giving no commands, recovery steps, or tolerance guidelines, so the bot could not provide concrete answers.

## Suggestion
Clearly document whether InfluxDB 3 Enterprise exposes CLI/API commands to trigger compaction, remove failed plans, and define operational limits when a compactor is down; if unavailable, state this explicitly and outline recommended recovery workflows.

## Conversations
- is there a way to manually start a compaction job on Enterprise3
- if compactor goes down, how long can cluster operate normally
- Can I manually trigger compaction in influxdb v3 enterprise?
- How to delete a compaction plan failed?

##### Relevant URLs

View coverage gap:
https://app.kapa.ai/720100f9-ce93-4305-88fd-5fcf71effad7/coverage-gaps/clusters/dd797c6e-ccd6-4adb-9777-0279c61b1101

Start with the linked coverage-gap page and the current documentation on automated scheduling. Verify the requested Enterprise compaction commands, failed-plan cleanup, and compactor-outage tolerance, then document available commands or explicitly record their absence with recovery guidance.

Written by the indexing model from the issue text.