feat: standardize package configuration and workflows

[Zaiidmo]

Standardization Pull Request

Changes

• ✅ Added standardized GitHub workflows (pr-validation, release-check, publish)
• ✅ Updated SONAR_PROJECT_KEY to CISCODE-MA_LoggingKit
• ✅ All checks passing: format, lint, typecheck, build

Status

• ✅ Format: Passing
• ✅ Lint: Passing
• ✅ Typecheck: Passing
• ✅ Build: Passing

All 7 packages now have identical standardized configuration and workflows.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
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

[Copilot]

Pull request overview

This PR appears to introduce a Changesets entry intended to drive a patch release for @ciscode/logging-kit, but the added release note text does not align with the PR’s stated goal of standardizing configuration/workflows.

Changes:

• Added a new Changesets file to bump @ciscode/logging-kit with a patch release note.

Comments suppressed due to low confidence (1)

.changeset/gold-chairs-pull.md:5

• Typo/inconsistent package name in the changeset text: use the actual package name "@ciscode/logging-kit" (with a hyphen) so release notes match the published package.

First release of @ciscode/loggingKit

[Copilot]

The changeset summary says this is the "First release", but the PR description indicates this PR is about standardizing configuration/workflows. Either update the changeset message (and bump type if needed) to describe the actual user-facing change, or remove the changeset if this PR has no consumer-facing impact.