feat: move EONET/GDACS to server-side with Redis caching (#983)

* feat: move EONET/GDACS to server-side with Redis caching and bootstrap hydration

Browser-direct fetches to eonet.gsfc.nasa.gov and gdacs.org caused CORS
errors and had no server-side caching. This moves both to the standard
Vercel edge → cachedFetchJson → Redis → bootstrap hydration pattern.

- Add proto definitions for NaturalService with ListNaturalEvents RPC
- Create server handler merging EONET + GDACS with 30min Redis TTL
- Add Vercel edge function at /api/natural/v1/list-natural-events
- Register naturalEvents in bootstrap SLOW_KEYS for CDN hydration
- Replace browser-direct fetches with RPC client + circuit breaker
- Delete src/services/gdacs.ts (logic moved server-side)

* fix: restore @ts-nocheck on generated files stripped by buf generate

docs/api/NewsService.openapi.yaml

@@ -169,15 +169,6 @@ components:
             required:
                 - provider
             description: SummarizeArticleRequest specifies parameters for LLM article summarization.
-        SummarizeStatus:
-            type: string
-            enum:
-                - SUMMARIZE_STATUS_UNSPECIFIED
-                - SUMMARIZE_STATUS_SUCCESS
-                - SUMMARIZE_STATUS_CACHED
-                - SUMMARIZE_STATUS_SKIPPED
-                - SUMMARIZE_STATUS_ERROR
-            description: SummarizeStatus indicates the outcome of a summarization request.
         SummarizeArticleResponse:
             type: object
             properties:
@@ -204,10 +195,17 @@ components:
                     type: string
                     description: Error type/name (e.g. "TypeError").
                 status:
-                    $ref: '#/components/schemas/SummarizeStatus'
+                    type: string
+                    enum:
+                        - SUMMARIZE_STATUS_UNSPECIFIED
+                        - SUMMARIZE_STATUS_SUCCESS
+                        - SUMMARIZE_STATUS_CACHED
+                        - SUMMARIZE_STATUS_SKIPPED
+                        - SUMMARIZE_STATUS_ERROR
+                    description: SummarizeStatus indicates the outcome of a summarization request.
                 statusDetail:
                     type: string
-                    description: Human-readable detail for non-success statuses (error message, skip reason, etc.).
+                    description: Human-readable detail for non-success statuses (skip reason, etc.).
             description: SummarizeArticleResponse contains the LLM summarization result.
         GetSummarizeArticleCacheRequest:
             type: object