fix!: bundle stream-browserify/process by default

[steabert]

Ever since the change away from automatically bundling browser-equivalents of Buffer and stream Node.js dependencies, there have been a number of issues with bundling. Since this is such a problem, the proposal is to fix it by including the bundle as default, prioritizing ease-of-use over bundle size.

The bundle size in most cases won't be affected however, so this change should go mostly unnoticed except for people using their own bundler (vite, CRA, webpack, etc) having less headaches.

For those very special use-cases where it's adamant to bundle manually, there is a "light" version of media-stream-library where you need to deal with the bundling yourself.

Fixes #754

[steabert]

Still checking some things, as the dependencies don't make much sense. If stream is not included in the bundling, the entire problem is actually shifted onto the bundler and the polyfill won't work anyway. It's probably not worth the effort to keep it external? The idea was to minimize total bundle size, but that would be for situations where someone is already using stream-browserify for another purpose not related to this library. This seems like an edge case.

Alternatively, we could bundle the default (i.e. heavy) and offer a light variant with nothing bundled or polyfilled, where you are on your own, for those specific cases. This would prioritize ease-of-use over advanced bundle size management. But seeing the large amount of issues come up after we stopped bundling all of this by default, I think it's probably worth it to flip priorities.

If using both player and streams it makes sense that the player has streams as external, since you don't want double that size, so there it does make sense.

EDIT: updated the PR accordingly.