Update rollup commonjs plugin to v22

Editor assessment

The `!` after `chore` correctly flags a breaking change, which fits a major plugin upgrade, and the Co-authored-by trailer is properly formatted per git conventions. What is missing is the companion `BREAKING CHANGE: ` footer: when a dependency jumps to a new major version, consumers need one or two lines describing what actually breaks — the `!` alone satisfies the letter of the spec but not its spirit of describing the impact. Typographically there is a stray double space before the PR number. Typing is also worth a second look: a dependency bump of this size often lands better as build(deps) or chore(deps) so release tooling can filter it. As written it is parseable and honest about breakage, but under-explained.