feat: add shared invalidate-changelog-cache composite action [ED-25349]

[Ntnelbaba]

Jira

https://elementor.atlassian.net/browse/ED-25349

Summary

• Adds actions/invalidate-changelog-cache, a composite action that POSTs to the marketing-plugins cache invalidate endpoint after a release.
• Endpoint URL is hardcoded: https://elementor.com/wp-json/elementor-site-product-changelog/v1/cache/invalidate
• Workflows pass api-key from repo secret ELEMENTOR_SITE_CHANGELOG_CACHE_INVALIDATE_API_KEY (WAF validation, same pattern as GlotPress import-originals).
• Supports explicit types input for split beta/dev invalidation, curl --max-time 60, and per-type failure tolerance.
• No-ops when the token secret is empty.

Consumers

• Internal: Invalidate site changelog cache after Core release [ED-25349] elementor#37036 — Core one-click + controlled release
• elementor/elementor-pro#7508 — Pro one-click release

Merge this first; consumer PRs reference @main.

Secret setup

Set ELEMENTOR_SITE_CHANGELOG_CACHE_INVALIDATE_API_KEY in elementor/elementor and elementor/elementor-pro.

Test plan

• Merge and confirm @main resolves.
• Set the API key secret to the WAF token value.
• Run a release workflow and confirm successful POSTs with api-key header.

✨ PR Description

1. Problem & Context

Automates the clearing of product changelog transients on Elementor.com to ensure users see updated release notes immediately after a deployment.

2. What Changed (Where)

• actions/invalidate-changelog-cache/action.yml: Created a composite action to handle cache invalidation requests.

3. How It Works

• Maps input channel to specific types (or uses types directly) and iterates through them.
• Sends authenticated POST requests to the site's WP-JSON endpoint via curl.
• Uses set -euo pipefail and --fail for basic error handling during execution.

Generated by LinearB AI and added by gitStream.
_{AI-generated content may contain inaccuracies. Please verify before using.
💡 Tip: You can customize your AI Description using Guidelines Learn how}

[Ntnelbaba]

What is this replace me?

[Ntnelbaba]

Removed REPLACE_ME — it was only a placeholder value when the repo secret was first created, not something workflows should check for. The action now skips only when the secret is empty.

Also addressed the bot feedback in the same commit: --max-time 60, per-type failures no longer abort the loop, and workflows can pass an explicit types input to split beta/dev invalidation.