feat: group dependency upgrades by upstream repository

[cryptodev-2s]

Explanation

@ethersproject has 11 packages here and they all ship from one repository at one version, so the 5.8.0 release produced #10478, #10481, #10482, #10483 and #10484, each bumping the same manifests and writing into the same changelogs. They cannot be merged independently without conflicting.

Scope	Repository	Packages here
@ethersproject	ethers-io/ethers.js	11
@yarnpkg	yarnpkg/berry	5
@docusaurus	facebook/docusaurus	5
@ethereumjs	ethereumjs/ethereumjs-monorepo	4

References

Follows #10451. Part of WPC-1161.

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them