chore: add package support metadata

[YfengJ]

Summary

• add npm homepage metadata pointing to the project README
• add npm bugs metadata pointing to the GitHub issues page

Why

The currently published @rsbuild/plugin-source-build package exposes its name, version, and repository on npm, but not homepage or bugs links. Adding these fields makes it easier for npm/package consumers to find documentation and report issues directly from package metadata.

Validation

• node -e "const pkg=require('./package.json'); if(pkg.homepage!=='https://github.com/rstackjs/rsbuild-plugin-source-build#readme') throw new Error('bad homepage'); if(!pkg.bugs || pkg.bugs.url!=='https://github.com/rstackjs/rsbuild-plugin-source-build/issues') throw new Error('bad bugs url'); console.log(JSON.stringify({homepage:pkg.homepage,bugs:pkg.bugs}, null, 2));"
• npm view @rsbuild/plugin-source-build@latest name version repository.url homepage bugs --json
• pnpm install --frozen-lockfile --ignore-scripts
• pnpm run lint
• pnpm run build
• pnpm run test
• npm pack --dry-run --ignore-scripts --json .
• git diff --check

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 98685477-110c-47fc-b2f7-1b2d9df6fcc9

📥 Commits

Reviewing files that changed from the base of the PR and between 6800d5a and 8f985f7.

📒 Files selected for processing (1)

• package.json

---

📝 Walkthrough

Walkthrough

The package.json for @rsbuild/plugin-source-build gains two new npm manifest fields: a homepage pointing to the GitHub repository readme URL and a bugs object containing the GitHub issues URL. No other files or package metadata were modified.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore: add package support metadata' accurately describes the main change of adding homepage and bugs fields to package.json metadata.
Description check	✅ Passed	The description is directly related to the changeset, explaining what metadata was added, why it matters for npm consumers, and providing comprehensive validation steps.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}