refactor(explore): simplify React keys in ViewQueryModal to match codebase patterns

Changed from content-based keys (item.query || item.error) to index-based
keys for the Fragment elements in ViewQueryModal. This aligns with
established Superset patterns (e.g., MarshmallowErrorMessage.tsx) for
displaying static API response data. Both approaches are technically
correct for static data, but index-based is simpler and more consistent.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: sadpandajoe

superset-frontend/src/explore/components/controls/ViewQueryModal.tsx

@@ -89,11 +89,9 @@ const ViewQueryModal: FC<Props> = ({ latestQueryFormData }) => {
 
   return (
     <ViewQueryModalContainer>
-      {result.map((item, index) => {
-        // Use content-based key when available, fall back to index
-        const key = item.query || item.error || `result-${index}`;
-        return (
-          <Fragment key={key}>
+      {result.map((item, index) => (
+        // Static API response data - index is appropriate for keys
+        <Fragment key={index}>
             {item.error && (
               <Alert type="error" message={item.error} closable={false} />
             )}
@@ -104,9 +102,8 @@ const ViewQueryModal: FC<Props> = ({ latestQueryFormData }) => {
                 language={item.language}
               />
             )}
-          </Fragment>
-        );
-      })}
+        </Fragment>
+      ))}
     </ViewQueryModalContainer>
   );
 };