[Website] Track blueprint resource type if the resource doesn't have a theme/plugin slug

[bgrgicak]

Motivation for the change, related issues

Blueprint analytics previously omitted the plugin/theme value when installPlugin/installTheme used a resource without a slug.

Implementation details

This records the resource type as the plugin/theme value when no slug is present, while preserving slug reporting for WordPress.org resources.

Testing Instructions (or ideally a Blueprint)

• CI

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Updates blueprint analytics so installPlugin/installTheme events always include a meaningful plugin/theme identifier by falling back to the resource type when no slug is available.

Changes:

• Log plugin/theme as slug || resource for installPlugin/installTheme steps.
• Update inline documentation to describe the fallback behavior.
• Add unit tests covering slug-present and slug-missing cases.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
packages/playground/website/src/lib/tracking.ts	Adds fallback logging of plugin/theme identifier when slug is missing.
packages/playground/website/src/lib/tracking.spec.ts	Adds vitest coverage for slug and slugless resource tracking behavior.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[ashfame]

Left a suggestion, rest looks good to go.

[ashfame]

Adding a prefix before logging resource type might be useful. resource:url and resource:git:directory. Otherwise, url just shows up as is, without any clue that it's not a plugin slug.

[bgrgicak]

Good point! I added it in 1ff63b3