Chore: Resolve vulnerabilities in transitive NPM dependencies

[imrraaj]

What

This PR adds overrides in package.json to address security vulnerabilities reported by Dependabot and npm audit.

Why

Fixes dependabot alerts

How

Testing Instructions

Screenshots

Additional Info

Checklist

• I have read the Contribution Guidelines.
• I have read the Development Guidelines.
• My code is tested to the best of my abilities.
• My code passes all lints (ESLint etc.).
• My code has detailed inline documentation.
• I have updated the project documentation as needed.
• I have added a changeset for this PR using npm run changeset.

[Copilot]

Pull request overview

This PR addresses reported security vulnerabilities in transitive npm dependencies by adding npm overrides, updating the npm lockfile resolution accordingly, and bumping the plugin release metadata to 1.1.2.

Changes:

• Added npm overrides to force patched versions of vulnerable transitive dependencies (e.g., minimatch, serialize-javascript, ajv).
• Updated package-lock.json to reflect the new override-driven dependency graph.
• Bumped plugin version/release metadata to 1.1.2 across WordPress readme, main plugin file, and changelog.

Reviewed changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
readme.txt	Updates WordPress “Stable tag” to 1.1.2.
package.json	Adds npm overrides for vulnerable transitive dependencies.
package-lock.json	Re-resolves dependency tree to apply overrides and related updates.
onemedia.php	Updates plugin header version and ONEMEDIA_VERSION constant to 1.1.2.
CHANGELOG.md	Adds 1.1.2 entry noting the security dependency resolution.

---

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

[Copilot]

The override ranges using ">=" (e.g., webpack-dev-server, minimatch, serialize-javascript) allow future major versions to be selected the next time the lockfile is regenerated, which can introduce breaking changes unrelated to the vulnerability fix. Prefer pinning to a specific patched version (or at least constraining to the current major with a caret/tilde range) to keep dependency resolution predictable.

Suggested change

	"serialize-javascript": ">=7.0.3",
	"serialize-javascript": "^7.0.3",