Publish aep.dev OpenAPI linter to npm with semantic versioning

[davidgagnearcherirm]

Problem

The AEP OpenAPI linter is currently only consumable via a GitHub URL and is not versioned.

As a result:

• Consumers cannot pin a specific version
• Breaking changes are introduced without an upgrade path
• Teams are forced to either fork the repo or continuously absorb breaking changes

Using a GitHub URL dependency only provides access to the latest state, which makes reproducible builds and controlled upgrades difficult.

Expected / Desired Behavior

• Linter is published to npm
• Releases follow semantic versioning
• Consumers can pin versions and upgrade intentionally

Proposed Solution

Publish the OpenAPI linter as a versioned npm package and tag releases accordingly.

See Spectral Documentation on Sharing Rulesets via NPM