ST-5444 Updating npm version to match LTS/Node stable pairing

[adammccullagh]

The current Internal node stable version includes an update to npm 10. Additionally, the .nvmrc file pins the LTS/hydrogen version - which too expects npm 10 as a pairing.

I have previously updated backpack-node-sass and bpk-svgs. These

The change is backwards compatible and thus this should only be a minor bump.

Remember to include the following changes:

• Ensure the PR title includes the name of the component you are changing so it's clear in the release notes for consumers of the changes in the version e.g [KOA-123][BpkButton] Updating the colour
• README.md (If you have created a new component)
• Component README.md
• Tests
• Storybook examples created/updated
• For breaking changes or deprecating components/properties, migration guides added to the description of the PR. If the guide has large changes, consider creating a new Markdown page inside the component's docs folder and link it here

[github-actions]

Visit https://backpack.github.io/storybook-prs/3204 to see this build running in a browser.

[github-actions]

Visit https://backpack.github.io/storybook-prs/3204 to see this build running in a browser.

[olliecurtis]

@adammccullagh I have changed the label and semver to be patch as the only thing that will affect the release is the bpk-svgs version bump in the packages folder. As any change to the root level package.json only impacts those running the project locally and not the production published version