Fix ESLint failures surfaced on the base PR's first lint run

Sub-PR workflows skip lint_test.yml (it triggers only on PRs targeting
master), so these slipped through into the integration branch:

- SimpleCommentScreen.jsx: pre-existing line-form disable for
  max-classes-per-file broke when #729 inserted `'use client'` ahead of
  it (the rule reports at file position 1:1; line-form disable on the
  import below no longer covered). Switch to a block-form disable at
  file top.
- ServerComponentsPage.jsx, LiveActivity.jsx, CommentsFeed.jsx:
  block-form disable for react/prop-types. React 19 removed runtime
  propTypes validation; the new components rely on ES default
  destructuring rather than dead PropTypes declarations.
- LiveActivityRefresher.jsx: line-form disable for
  react/no-unstable-nested-components on the ErrorBoundary's
  fallbackRender prop. The render-prop API is canonical for
  react-error-boundary when the fallback needs a closure; it cannot be
  hoisted without losing access to parent state (refreshKey,
  setRefreshKey, refetchComponent via buildRetry).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: ihabadham

client/app/bundles/comments/components/SimpleCommentScreen/ror_components/SimpleCommentScreen.jsx

@@ -1,6 +1,6 @@
+/* eslint-disable max-classes-per-file */
 'use client';
 
-// eslint-disable-next-line max-classes-per-file
 import React from 'react';
 import request from 'axios';
 import Immutable from 'immutable';

client/app/bundles/server-components/components/CommentsFeed.jsx

@@ -1,3 +1,5 @@
+/* eslint-disable react/prop-types -- React 19 no longer validates propTypes at runtime; using ES default destructuring instead */
+
 import React from 'react';
 import { Marked } from 'marked';
 import { gfmHeadingId } from 'marked-gfm-heading-id';

client/app/bundles/server-components/components/LiveActivityRefresher.jsx

@@ -70,6 +70,9 @@ const LiveActivityRefresher = () => {
         <span className="text-xs text-slate-500 ml-2">Refresh count: {refreshKey}</span>
       </div>
       <ErrorBoundary
+        // react-error-boundary's fallbackRender is a render-prop API by design;
+        // the closure captures buildRetry which depends on parent state.
+        // eslint-disable-next-line react/no-unstable-nested-components
         fallbackRender={({ error, resetErrorBoundary }) => (
           <div className="bg-rose-50 border border-rose-200 rounded-lg p-4">
             <p className="text-rose-700 font-semibold mb-1">Server component fetch failed</p>

client/app/bundles/server-components/ror_components/LiveActivity.jsx

@@ -1,3 +1,5 @@
+/* eslint-disable react/prop-types -- React 19 no longer validates propTypes at runtime; using ES default destructuring instead */
+
 import React from 'react';
 import os from 'os';
 

client/app/bundles/server-components/ror_components/ServerComponentsPage.jsx

@@ -2,6 +2,8 @@
 // It can use Node.js APIs and server-only dependencies directly.
 // None of these imports are shipped to the client bundle.
 
+/* eslint-disable react/prop-types -- React 19 no longer validates propTypes at runtime; using ES default destructuring instead */
+
 import React, { Suspense } from 'react';
 import ServerInfo from '../components/ServerInfo';
 import CommentsFeed from '../components/CommentsFeed';