Service parameter to enable console independently from accelerated mode or file explorer

[javuto]

Summary

Decouples per-node Console and File Explorer availability from accelerated query polling.

This adds a dedicated osquery.console feature switch, keeps File Explorer behind its own osquery.fileExplorer switch, and leaves osquery.accelerated as an optional fast-polling enhancement instead of a required dependency.

Changes

• Added osquery.console config support.
• Added --osquery-console / OSQUERY_CONSOLE.
• Added console to /api/v1/features.
• Gated Console API routes behind osquery.console.
• Gated File Explorer API routes behind osquery.fileExplorer without requiring osquery.accelerated.
• Updated TLS acceleration checks so active Console/File Explorer sessions only request fast polling when acceleration is enabled.
• Updated frontend Console visibility to use features.console.
• Updated sample config comments and service-config field descriptions.
• Adjusted priming UI copy from “accelerating” to “warming”.

Validation

• GOCACHE=/tmp/osctrl-gocache go test ./pkg/config ./pkg/console ./pkg/fileexplorer ./cmd/api ./cmd/api/handlers ./cmd/tls/handlers
• cd frontend && npm test -- NodeDetailPage.test.tsx NodeConsolePage.test.tsx NodeFileExplorerTab.test.tsx
• cd frontend && npm run check
• git diff --check