feat: Enhance frontend loading experience and service status handling

### Summary of Changes
- Removed proxy configuration in `rsbuild.config.js` as the API Gateway is not running.
- Added smooth transitions and gentle loading overlays in CSS for improved user experience during data loading.
- Updated `Dashboard` component to conditionally display loading spinner and gentle loading overlay based on data fetching state.
- Enhanced `useOfflineAwareServiceStatus` and `useOfflineAwareSystemData` hooks to manage loading states and service status more effectively.
- Increased refresh intervals for service status and system data to reduce API call frequency.

### Expected Results
- Improved user experience with smoother loading transitions and better feedback during data refreshes.
- Enhanced handling of service status checks, providing clearer information when services are unavailable.
- Streamlined code for managing loading states, making it easier to maintain and extend in the future.

services/service-adapters/models/schemas.py

@@ -6,7 +6,11 @@ from pydantic import BaseModel, Field
 class ServiceStatus(BaseModel):
     enabled: bool = Field(..., description="Whether the service is enabled")
     url: str = Field(..., description="Service URL")
-    status: str = Field(..., description="Service status")
+    status: str = Field(..., description="Service status (healthy, unhealthy, disabled, error, timeout, unauthorized, forbidden)")
+    response_time: Optional[float] = Field(None, description="Response time in seconds")
+    error: Optional[str] = Field(None, description="Error message if status is not healthy")
+    uptime: Optional[str] = Field(None, description="Service uptime information (for sensor-based checks)")
+    metadata: Optional[Dict[str, Any]] = Field(default_factory=dict, description="Additional metadata from health check")
 
 
 class HAAttributes(BaseModel):