feat(DX-7525): migrate contentstack-cli-content-type v1 into cli-plugins monorepo

[cs-raj]

Summary

Migrates the contentstack-cli-content-type standalone plugin into the cli-plugins pnpm monorepo at packages/contentstack-content-type, targeting the CLI v1 line (version 1.5.0, npm tag latest).

The npm package name is unchanged (contentstack-cli-content-type). All 6 commands (content-type:list, details, audit, compare, compare-remote, diagram) and their flags are identical to the standalone version.

---

What's included

New package — packages/contentstack-content-type/

Area	Details
Source	src/commands/content-type/ (6 commands), src/core/, src/utils/, src/types/, src/config/
Tests	16 Jest + ts-jest test files under tests/ — commands, core logic, HTTP client, utils
Bin	bin/run, bin/run.js, bin/run.cmd, bin/dev, bin/dev.js, bin/dev.cmd
Config	package.json (v1.5.0, v1 CLI deps, pnpm-aligned scripts, monorepo repo/homepage), tsconfig.json (composite), jest.config.js, .eslintrc
Docs	AGENTS.md, README.md, SECURITY.md, LICENSE, screenshots/
Skills	4 skill files under skills/ (dev-workflow, testing, code-review, contentstack-cli-content-type) — all reference pnpm commands and the production release workflow

Monorepo config changes

File	Change
.github/workflows/release-production-plugins.yml	Added Publishing content-type (Production) step (tag: latest) between query-export and Create Production Release
.github/workflows/unit-test.yml	Added Run tests for Contentstack Content Type plugin step (npm run test:unit)
.github/config/release.json	Added "content-type": false alongside existing v1 plugin keys
.cursor/rules/README.md	Added contentstack-content-type to the monorepo package list
README.md	Added content-type plugin to Useful Plugins section
AGENTS.md	New file (v1 branch); includes Content Type section with v1 dep ranges and Jest note
CONTENT-TYPE-MIGRATION.md	New migration guide; documents repo/issue tracking change, v1 (1.5.0 / latest) and v2 (2.0.0-beta.0 / beta) version lines, install, local dev, archive instructions
pnpm-lock.yaml	Regenerated with v1 CLI deps resolved
.talismanrc	Updated pnpm-lock.yaml checksum

---

Key decisions

• v1 CLI deps — @contentstack/cli-command ^1.8.2 and @contentstack/cli-utilities ^1.18.3 match the standalone repo and the v1 line of every other plugin on this branch.
• Version 1.5.0 — minor bump from 1.4.6 to mark the first release from the monorepo; no breaking changes, all commands and flags unchanged.
• tag: latest — production release workflow, consistent with all other v1 plugins on this branch.
• Jest retained — the source plugin uses Jest + ts-jest with 80 % global coverage thresholds. Rewriting 16 test files to Mocha/Chai is deferred; the CI step uses npm run test:unit consistent with monorepo convention.
• release-production-plugins.yml not release-v2-beta-plugins.yml — the v2 beta release workflow does not exist on this branch; the production workflow with tag: latest is the correct target for v1.

---

Test plan

• pnpm --filter contentstack-cli-content-type run build completes without errors
• pnpm --filter contentstack-cli-content-type run test — all 16 test files pass
• pnpm --filter contentstack-cli-content-type run test:coverage — 80 % global thresholds met
• pnpm --filter contentstack-cli-content-type run lint — ESLint clean
• Full monorepo build passes: NODE_ENV=PREPACK_MODE npm run build
• csdx plugins:link inside packages/contentstack-content-type then csdx content-type:list -a <alias> returns content types
• Existing packages unaffected — no regressions in monorepo unit-test workflow

[github-actions]

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type	Count (with fixes)	Without fixes	Threshold	Result
🔴 Critical Severity	0	0	10	✅ Passed
🟠 High Severity	0	0	25	✅ Passed
🟡 Medium Severity	0	1	500	✅ Passed
🔵 Low Severity	0	0	1000	✅ Passed

⏱️ SLA Breach Summary

⚠️ Warning: The following vulnerabilities have exceeded their SLA thresholds (days since publication).

Severity	Breaches (with fixes)	Breaches (no fixes)	SLA Threshold (with/no fixes)	Status
🔴 Critical	0	0	15 / 30 days	✅ Passed
🟠 High	0	0	30 / 120 days	✅ Passed
🟡 Medium	0	1	90 / 365 days	⚠️ Warning
🔵 Low	0	0	180 / 365 days	✅ Passed

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:

• Critical without fixes: 0
• High without fixes: 0
• Medium without fixes: 1
• Low without fixes: 0

⚠️ BUILD PASSED WITH WARNINGS - SLA breaches detected for issues without available fixes

Consider reviewing these vulnerabilities when fixes become available.

[github-actions]

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type	Count (with fixes)	Without fixes	Threshold	Result
🔴 Critical Severity	0	0	10	✅ Passed
🟠 High Severity	0	1	25	✅ Passed
🟡 Medium Severity	2	2	500	✅ Passed
🔵 Low Severity	0	0	1000	✅ Passed

⏱️ SLA Breach Summary

⚠️ Warning: The following vulnerabilities have exceeded their SLA thresholds (days since publication).

Severity	Breaches (with fixes)	Breaches (no fixes)	SLA Threshold (with/no fixes)	Status
🔴 Critical	0	0	15 / 30 days	✅ Passed
🟠 High	0	0	30 / 120 days	✅ Passed
🟡 Medium	0	1	90 / 365 days	⚠️ Warning
🔵 Low	0	0	180 / 365 days	✅ Passed

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:

• Critical without fixes: 0
• High without fixes: 1
• Medium without fixes: 2
• Low without fixes: 0

⚠️ BUILD PASSED WITH WARNINGS - SLA breaches detected for issues without available fixes

Consider reviewing these vulnerabilities when fixes become available.