Add repository metadata to published packages

[9cathyface8-cyber]

Summary

Adds npm repository metadata to the published Cloudflight ESLint packages.

Problem

The published packages expose homepage and bugs metadata, but not repository metadata. For example:

npm view @cloudflight/eslint-plugin-typescript@1.3.3 name version repository homepage bugs --json

returns homepage and bugs, but no repository field.

Reproduction

From the npm registry:

npm view @cloudflight/eslint-plugin-typescript@1.3.3 name version repository homepage bugs --json
npm view @cloudflight/eslint-plugin-react@1.3.3 name version repository homepage bugs --json
npm view @cloudflight/eslint-plugin-angular@1.3.3 name version repository homepage bugs --json
npm view @cloudflight/eslint-plugin-vue@1.3.3 name version repository homepage bugs --json
npm view @cloudflight/eslint-plugin-node@1.3.3 name version repository homepage bugs --json

Each package currently omits repository.

Root Cause

The package manifests include support links, but do not declare the monorepo repository metadata for each published workspace package.

Fix

Add repository objects to the five published package manifests, including the monorepo URL and the correct directory for each package.

Tests

• git diff --check
• Node JSON assertion for all added repository values
• npm pack --dry-run --ignore-scripts --json ./packages/eslint-plugin-angular
• npm pack --dry-run --ignore-scripts --json ./packages/eslint-plugin-node
• npm pack --dry-run --ignore-scripts --json ./packages/eslint-plugin-react
• npm pack --dry-run --ignore-scripts --json ./packages/eslint-plugin-typescript
• npm pack --dry-run --ignore-scripts --json ./packages/eslint-plugin-vue

Bounty

This PR is intended to support the public microbounty lead at charles-openclaw/charles-microbounties#1469 for the missing npm repository metadata.