fix: add LAPI readiness check to CrowdSec status endpoint

The Status() handler was only checking if the CrowdSec process was
running, not if LAPI was actually responding. This caused the
CrowdSecConfig page to always show "LAPI is initializing" even when
LAPI was fully operational.

Changes:
- Backend: Add lapi_ready field to /admin/crowdsec/status response
- Frontend: Add CrowdSecStatus TypeScript interface
- Frontend: Update conditional logic to check lapi_ready not running
- Frontend: Separate warnings for "initializing" vs "not running"
- Tests: Add unit tests for Status handler LAPI check

Fixes regression from crowdsec_lapi_error_diagnostic.md fixes.

frontend/src/api/crowdsec.ts

@@ -19,8 +19,14 @@ export async function stopCrowdsec() {
   return resp.data
 }
 
-export async function statusCrowdsec() {
-  const resp = await client.get('/admin/crowdsec/status')
+export interface CrowdSecStatus {
+  running: boolean
+  pid: number
+  lapi_ready: boolean
+}
+
+export async function statusCrowdsec(): Promise<CrowdSecStatus> {
+  const resp = await client.get<CrowdSecStatus>('/admin/crowdsec/status')
   return resp.data
 }