bug: mongodb has to be a peer dependency

[plushdohn]

The mongodb package is leaving some disgusting warning logs whenever it's first loaded inside the app that uses Catalyst:

This has only started happening since Catalyst was moved to a separate package. When the source files were part of the Next project, no such logs were visible.

I have no idea what is causing this, I thought it might have to do with mongodb being wrongfully imported in the browser but I don't see where or how this is happening.

[plushdohn]

Ok so I found out two things:

• Someone opened an issue on the Next repo for the exact same reason, but they were using Mongoose.
• This doesn't happen if MongoDB is a direct dependency of the Next.js app that's running Catalyst.

This means that this error only occurs when MongoDB is used internally by a package that's then imported in the Next app (as is the case with Mongoose or Catalyst), and that we can temporarily fix it by making mongodb a peer dependency in our core package.

This is far from ideal as we don't really want the user to care about having mongodb in their dependencies, but for now it allows us to develop comfortably, and some package managers at least auto-install peer dependencies so it's not that bad.