Collections fix version lookup

[josephjclark]

Short Description

If you specify the collections versions number (as I do in local testing), everything works fine.

But if the worker looks up the latest collections version from npm, everything breaks!

This is because:

a) I am saving the adaptor version to the wrong place so it doesn't get used (whoops)
b) the version number includes whitespace, which breaks the autoinstall command.

AI Usage

Please disclose how you've used AI in this work (it's cool, we just want to know!):

• Code generation (copilot but not intellisense)
• Learning or fact checking
• Strategy / design
• Optimisation / refactoring
• Translation / spellchecking / doc gen
• Other
• I have not used AI

You can read more details in our Responsible AI Policy

Release branch checklist

Delete this section if this is not a release PR.

If this IS a release branch:

• Run pnpm changeset version from root to bump versions
• Run pnpm install
• Commit the new version numbers
• Run pnpm changeset tag to generate tags
• Push tags git push --tags

Tags may need updating if commits come in after the tags are first generated.