https://sonarly.com/issue/40483?type=bug
Duplicate-record detection still works in backend and legacy UI code, but it is no longer reachable from the record show page after the old show-page path was removed.
Fix: I fixed the regression in the frontend layer where record show pages now render through page-layout widgets instead of the old `RecordFieldList` path.
### What I changed
- Updated `FieldsWidget` to render `RecordDetailDuplicatesSection` for full record pages (not side panels).
- This restores duplicates visibility in the same place users now see core record fields on record show pages, without introducing a new widget type or generated-schema changes.
### Why this fixes user impact
- Person/Company default record pages already use the `FIELDS` widget on the Home tab.
- By attaching duplicates rendering to `FieldsWidget`, duplicate suggestions become reachable again in the current page-layout-based show flow.
- `RecordDetailDuplicatesSection` already encapsulates:
- duplicate-criteria gating,
- duplicate query call,
- null rendering when no duplicates,
- merge action affordance.
Authored by Sonarly by autonomous analysis (run 46155).