fix: add .ts extensions to all relative imports for Vite native config loader compatibility

[felladrin]

Root Cause

Vite's upcoming native config loader (planned default in next major) requires explicit file extensions on all relative imports. The server codebase was using extensionless imports, triggering warnings during docker compose up.

Changes

Added .ts extensions to all relative imports across 11 files:

File	Imports Fixed
vite.config.ts	10 server hook imports
server/internalApiEndpointServerHook.ts	3 imports
server/configEndpointServerHook.ts	1 import
server/searchEndpointServerHook.ts	5 imports
server/statusEndpointServerHook.ts	4 imports
server/rerankerServiceHook.ts	2 imports
server/rerankerService.ts	1 import
server/webSearchService.ts	1 import
server/rankSearchResults.ts	1 import
server/handleTokenVerification.ts	1 import
server/verifyTokenAndRateLimit.ts	2 imports

Verification

Ran docker compose up and confirmed no import extension warnings in logs. Server starts cleanly.