Dashboard: prevent domain card column controls from appearing on right-click

[agent-sandbox-automattic]

Fixes DOTMSD-1316

Proposed Changes

• In useFields(), when inOverview is true, map all returned fields to have enableHiding: false.

Why are these changes being made?

The domain info card on the site overview page renders a DataViews table using only DataViews.Layout and DataViews.Pagination sub-components — not the full toolbar. This means column controls are intentionally absent from the visible UI.

However, right-clicking on a column header still surfaced the column selection interface because some domain fields (owner, ssl_status, and is_primary_domain) had enableHiding: true (or no explicit enableHiding: false). @wordpress/dataviews shows the "Manage columns" context menu option whenever any field in the fields array is hideable.

Setting enableHiding: false on all fields when inOverview is true tells DataViews there are no user-manageable columns, so the column selection interface is suppressed from both the toolbar (already hidden by using sub-components) and the right-click context menu.

Testing Instructions

1. Navigate to a site overview page in the multi-site dashboard.
2. Scroll to the Domain names card.
3. Right-click on any column header in the domain table (e.g. "Paid until" or "Status").
4. Before: A context menu with a "Manage columns" or column selection option appeared.
5. After: No column management option appears in the context menu.

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• For UI changes, have you tested the affected components in dark mode?
• Have you tested accessibility for your changes? Ensure the feature remains usable with various user agents (e.g., browsers), interfaces (e.g., keyboard navigation), and assistive technologies (e.g., screen readers) (PCYsg-S3g-p2).
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
  • For UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
• For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

---

Linear: DOTMSD-1316

Co-authored-by: p-jackson philip.jackson@automattic.com

This PR was auto-generated by Agent Sandbox. Please review carefully before merging.

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-184159

Jetpack Cloud Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-184159&env=jetpack

Automattic for Agencies Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-184159&env=a8c-for-agencies

Dashboard Live (dotcom) (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-184159&env=dashboard

Dashboard Live (A4A) (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-184159&env=dashboard-a4a

[matticbot]

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

• help-center
• notifications

To test WordPress.com changes, run install-plugin.sh $pluginSlug ai/agent/dotmsd-1316-1781840439 on your sandbox.