fix: package.json homepage links to use the main branch

[chad3814]

Description

So with the fast-xml-parser vulnerability I was trying to trace down if updating would help, and I started at the npm package page for @aws-sdk/core. The homepage link was out of date and led to a 404.

I looked at the package.json files in clients/* and packages/* looking for homepage values not using the main branch, and corrected them to main.

Testing

No code testing, a documentation change.

Checklist

• If you wrote E2E tests, are they resilient to concurrent I/O?
• If adding new public functions, did you add the @public tag and enable doc generation on the package?

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.