Enhance duplicate page action

[rchlfryn]

Description

Improves the page duplication and provisioning logic introduced in #974. The clearLayoutRelationships utility properly clears relationship and upload fields from any block — keeping the block structure intact and letting editors repopulate the tenant-specific references.

Provisioning is now driven by DVAC's navigation structure. It queries the template tenant's published navigation to determine which pages and built-in pages to create — only pages referenced in navigation are provisioned. Pages are created as blank published pages (title, slug, empty content block) with no copied content. Built-in pages are also filtered to those referenced in the navigation. Navigation and all pages are published immediately. The duplicatePageToTenant action still uses clearLayoutRelationships to copy layout structure while clearing tenant-specific references, and now only appends " - Copy" to the title/slug when a page with the same slug already exists for the target tenant.

The clearLayoutRelationships utility currently handles all field types in Payload's schema (group, array, tabs, row, collapsible, richText with Lexical blocks), including Lexical-embedded blocks like ButtonBlock and CalloutBlock. If new field container types are added to Payload in the future, the utility would need updating.

Related Issues

Part of #533 (follow-up to #974)
Closes #625

Key Changes

• Navigation-driven provisioning — queries DVAC's published navigation to extract referenced page slugs and built-in page URLs via extractNavReferences. Only pages and built-in pages that appear in the navigation are created for the new tenant. If DVAC's navigation changes, provisioning automatically adjusts.
• clearLayoutRelationships utility — recursively clears relationship and upload fields from any block in a page layout (including nested groups, arrays, tabs, and Lexical rich-text blocks with ButtonBlock and CalloutBlock), keeping structure intact so editors repopulate tenant-specific references after duplication.
• Provisioning creates blank published pages — pages use DVAC's titles and slugs but contain only an empty content block. Navigation and pages are published immediately.
• Conditional " - Copy" suffix — duplicatePageToTenant now only appends " - Copy" to the title and "-copy" to the slug when a page with the same slug already exists for the target tenant.
• Bug fix — duplicatePageToTenant was spreading the cleaned layout array into data instead of assigning it as data.layout.
• Tests — unit tests for clearLayoutRelationships (relationships, uploads, groups, arrays, tabs, Lexical blocks, id stripping) and integration tests for duplicatePageToTenant (slug conflict and no-conflict cases), backed by a shared fixtures/mockBlocks.ts.

How to test

Added tests

1. pnpm seed to get a fresh database with the DVAC template tenant
2. Provisioning: Create a new avalanche center in the admin panel. Verify the onboarding checklist shows automated steps as complete. Only pages and built-in pages referenced in DVAC's navigation are created. Pages are blank (empty content block) and published.
3. Duplicate to Tenant: Open any published page on DVAC → ⋮ menu → "Duplicate to Tenant" → pick another tenant. Verify the new page is created as a draft with the original title/slug (no " - Copy" if no conflict), relationship fields are cleared (empty), and non-relationship fields (text, colors, layout structure) are preserved.

Screenshots / Demo video

Duplicate page to... demo
Provisioning tenant demo

Migration Explanation

No schema changes — no migration needed.

Future enhancements

Should we include ButtonBlock & CalloutBlock in DEFAULT_BLOCKS? They are the only 2 not included. #1001

[github-actions]

Preview deployment: https://duplicate-to-enhance.preview.avy-fx.org

[busbyk]

One relationship removal isn't working (ButtonBlock inside of a richText field in EventList (likely BlogList too)): https://www.loom.com/share/777dddf99b784ec7b60e67ffa792a844

[rchlfryn]

One relationship removal isn't working (ButtonBlock inside of a richText field in EventList (likely BlogList too))

Good catch! ButtonBlock & CalloutBlock are the only 2 not included in DEFAULT_BLOCKS? I added a note under Future Enhancement of this PR to make an issue since I do not want to scope creep this PR.

I added ButtonBlock & CalloutBlock to the allBlocksMap in clearLayoutRelationships so it will copy as expected now.