Allow Helia to be used without mandating dependencies on every transport

[justin0mcateer]

In #127 'defaults' were added so that Helia could be used 'plug and play' without providing any of it's necessary dependencies. That is great for people just trying it out for the first time. However, when trying to build an application on top of Helia, this creates a significant amount of unnecessary transitive dependencies that can be problematic in their own right.

Could there be some way to perhaps create a 'bare bones' package that doesn't provide the 'defaults' that a 'new user friendly' package could depend on, then adding the defaults on top?

There really isn't a great way to work around this problem, as solutions like patching the package often aren't tenable on artifacts like the 'package.json'.

[SgtPooki]

I am open to this and think it could be very useful. @achingbrain Would you be okay with this?

[justin0mcateer]

With 3.0 coming up, any more thoughts on this?