Implement Pendo JavaScript library (Page/Feature events)

[chriszarate]

Description

Provide Pendo-based telemetry for client-side Pendo Page/Feature events. These events require a client library to be enqueued and configured. "Track events" can also be sent client-side, but we should avoid this and prefer the server-side implementation.

Usage requires a single static function call to enable the client-side library (Pendo::enable_javascript_library()).

Pre-review checklist

Please make sure the items below have been covered before requesting a review:

• This change works and has been tested locally or in Codespaces (or has an appropriate fallback).
• This change works and has been tested on a sandbox.
• This change has relevant unit tests (if applicable).
• This change uses a rollout method to ease with deployment (if applicable - especially for large scale actions that require writes).
• This change has relevant documentation additions / updates (if applicable).
• I've created a changelog description that aligns with the provided examples.

Pre-deploy checklist

• VIP staff: Ensure any alerts added/updated conform to internal standards (see internal documentation).

Steps to Test

[smithjw1]

Question about how enablement is controlled. I see the edit_posts restriction, but not the other items mentioned here. As well a check to a org level opt out (synced from GOOP).

[chriszarate]

I see the edit_posts restriction, but not the other items mentioned here.

@smithjw1 These checks were initially separated. I updated the code and added tests In a way that should make it more obvious and reviewable.

• ✅ Nonproduction Environments. Covered by Pendo::is_pendo_enabled_for_environment()
• ✅ Where our plugin is installed. Not enforced by mu-plugins, but instead de facto covered by the absence of plugin code calling Pendo::enable_javascript_library()
• ✅ Only for users with edit_posts capability
• ⛔ On certain URLs. Per this comment I did not implement this restriction.
• ✅ Outside of VIP. Covered by Pendo::is_pendo_enabled_for_environment()

As well a check to a org level opt out (synced from GOOP).

That is implemented in two ways:

1. The presence of VIP_DISABLE_PENDO_TELEMETRY=true which disables all Pendo telemetry.
2. The absence of VIP_PENDO_SNIPPET_API_KEY which disables just the snippet enqueuing.

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud