This cascade of dependencies will be hard to deal with, but if you want just to test, you can use all of them as local packages, so it should work as they will use the version of your local Meteor app.
If they don’t work, you can just add the version in the package.js.
Your problem here will be with packages not compatible in runtime with Meteor 3.
For example, collection2, I don’t see any commits about Meteor 3.
My goal with the effort that I’m starting is to discover the incompatibilities and start to provide PRs or alternative packages.
As Quave has many packages and apps, if we can make our apps work with Meteor 3, that will help many other companies as we use Meteor quite a lot.
But again, this work will take weeks, if not months, because there will be cases where the package changes will be challenging.
We are starting with our template, which is an almost empty Meteor app (template).