[Website] Add analytics for Dock and site tools - #4381

What is this PR doing?

Adds 28 Google Analytics events for Dock layouts and tool usage, New Playground tab selection and creation, site settings, Blueprint actions, database tools, file editing, log searches, email selection, exports, address-bar navigation, terminal commands, and the permanent-storage action.

Motivation for the change, related issues

Measure which Playground tools people use without treating background saves or every search keystroke as separate user actions.

Implementation details

• Reuses logTrackingEvent and its typed event names. Payloads contain layout, corner, tool, action, toggle state, creation type, settings choices, Blueprint execution target, or public gallery Blueprint paths. These new events do not include local file paths, user-entered Blueprint URLs, search text, terminal code, email contents, or shared URLs.
• dockMoved fires once the Dock finishes converting into its left or right corner button. Moving a floating Dock without folding it does not emit this event.
• fileOpen tracks files selected by the user. Automatically opening the initial file does not emit an event.
• siteSettingsChanged fires once after a successful settings submission, with the submitted PHP version, WordPress version, language, networking, and multisite values. Draft edits, canceled changes, and failed submissions emit no event.
• dockItemClick includes the selected tool and action: 'open' | 'close'.
• blueprintCopyUrl fires after the unsupported-bundle guard passes.
• storePermanently tracks opening the permanent-storage pane through the save-status indicator, not completed storage.
• fileSave uses an optional PlaygroundFileEditor.onManualSave callback for explicit saves with pending edits, including the Save button and keyboard shortcut. Autosaves, file creation, and cleanup writes are excluded. Events track initiation rather than successful completion.
• logsSearch fires after a 500 ms pause in typing. Empty searches and pending searches cleared or unmounted before the delay are excluded; filtering still updates immediately.
• dockDevToolsToggle tracks clicks on Dev Tools with the resulting state (expanded or collapsed).
• newPlaygroundTabClick reports the selected creation tab in type, including keyboard activation and arrow-key navigation. createPlayground reports creation actions with type: vanilla, gallery, blueprint-url, write-own, pull-request, github, or zip. Vanilla WordPress uses vanilla; gallery Blueprints use gallery and include their public blueprint path loaded from the WordPress/blueprints gallery index; GitHub reports once when creating the import target, even if saved-site creation falls back to a temporary site; PR previews report after verification when navigation begins; ZIP imports report for both file selection and drag-and-drop. Creation events contain the source type and, for gallery Blueprints, the public Blueprint path. User-entered Blueprint URLs are not included.
• Other events track their UI action. In particular, exportGitHub tracks opening the export form.
• No breaking API changes.

Testing Instructions

Run the website type check and targeted tracking, PR-preview, settings-submission, and file-editor suites from the repository root:

nvm use
npx nx run playground-website:typecheck
npx nx run playground-website:test --testFile=tracking.spec.ts --testFile=src/github/preview-pr/form.spec.tsx --testFile=use-site-settings-submission.spec.tsx
npx nx run playground-components:test:vite --testFile=playground-file-editor.spec.tsx

Setup and observe events

1. Run nvm use, install dependencies with npm ci if needed, and start the website with npm run dev.
2. Open http://127.0.0.1:5400/website-server/ and browser DevTools. In packages/playground/website/src/lib/tracking.ts, temporarily add console.log('Tracking', event, data); at the start of logTrackingEvent, before its try block. Do not commit this debugging line. This works locally even when Google Analytics is not configured. Clear the console between checks.

Corrected behavior

3. Open Logs. If it is empty, open Terminal in PHP mode and run trigger_error('Analytics test notice', E_USER_NOTICE);, then return to Logs. Type notice continuously: filtering updates immediately, with no per-character events, then exactly one logsSearch after a 500 ms pause. Clear the input: no search event. Type and clear a query before 500 ms: no event. No search text is logged.
4. Open Files. Automatically opening wp-config.php must not emit fileOpen. Select a disposable file and confirm one fileOpen. Opening and creating files must not emit fileSave. Edit the file and wait for autosave (about 1.5 seconds): changes save with no fileSave. Edit again and click Save before autosave: exactly one fileSave. Repeat using Cmd/Ctrl+S: exactly one event. Save without pending edits: no event.
5. Close the tool pane and keep the Dock floating. Drag the Dock horizontally without folding it: no dockMoved. Drag it beyond the left edge until it converts into a corner button: one dockMoved with position: 'left-corner' after conversion. Restore it with the corner button and repeat on the right: one event with position: 'right-corner'.

Remaining event coverage

6. Reload in floating and full-width modes; repeat with a mobile viewport. Check dockInitialLayout.layout is floating, full-width, or mobile. Toggle full width (dockLayoutChanged), hide/show tools (dockCollapsed/dockExpanded), and click each of the ten Dock tools (dockItemClick with the selected section and action: 'open'). Click the active tool again to close its pane: expect action: 'close'.
7. In Site Settings, change PHP several times and close the pane without submitting: expect no siteSettingsChanged. Reopen settings, change PHP or network access, and apply the changes: expect one event after success, containing phpVersion, wpVersion, language, networkAccess, and multisite. Change WordPress version, language, or multisite and create a fresh Playground: expect one event after success with the submitted values. Failed submissions must emit no event.
8. In Blueprint, copy a single-file Blueprint URL, download its ZIP, and run it. Check blueprintCopyUrl, blueprintDownload, and blueprintRun with the appropriate target (new-playground for an autosaved site). Attempt to copy a Blueprint bundle URL: expect the unsupported-link alert and no blueprintCopyUrl.
9. In Database, open Adminer and phpMyAdmin and download the SQLite database: databaseOpenAdminer, databaseOpenPhpMyAdmin, and databaseDownload. Selecting a file in Files emits fileOpen.
10. Run a harmless PHP snippet and wp core version in Terminal: terminalRunPHP and terminalRunWpCli. Run wp_mail('analytics-test@example.test', 'Analytics test', 'Captured locally');, then click the captured message in Email: emailSelect.
11. In Export, download the site ZIP, copy the setup link, and open Export to GitHub: exportDownload, exportLink, and exportGitHub. There is no need to authenticate or publish. Choose an address-bar suggestion and refresh: addressBarSuggestion and addressBarRefresh.

New Playground and Dev Tools

12. Click Dev Tools to expand and collapse it. Each click emits one dockDevToolsToggle with the resulting state.
13. Open New Playground and select each of the six tabs. Confirm newPlaygroundTabClick reports the selected tab in type; repeat using keyboard activation and arrow keys. Opening the pane or switching tabs must not emit createPlayground.
14. Start a Playground from Vanilla WordPress and another gallery Blueprint, a Blueprint URL, an authored Blueprint, a verified PR, a GitHub import, and a Playground ZIP. Confirm one createPlayground at creation initiation with the corresponding type: vanilla, gallery, blueprint-url, write-own, pull-request, github, or zip. Gallery events must include the public blueprint path; user-entered Blueprint URLs must not appear in event data. Repeat ZIP import by dropping a file. Empty Blueprint URLs, invalid authored Blueprints, canceled file pickers, and non-ZIP files must not emit creation events. PR lookup or repository selection alone must not emit a creation event before verification allows navigation.
15. Click the Autosaved or Unsaved status to open permanent storage: expect one storePermanently. This tracks opening the pane, not completing storage.

Summary by CodeRabbit

• Other Improvements
  • Added tracking for Playground creation and navigation, Blueprint actions, dock and address-bar interactions, file and database activity, site settings, email selection, log searches, exports, and terminal commands.
  • File opens and manual saves now trigger tracking events; autosaves and saves without pending edits do not.