fix(build): provide esm package

[ShGKme]

It seems, this library conflicts with the current @nextcloud/webpack-vue-config v5.5.0.

It provides only cjs module that consider Vue package to be cjs as well.
But apps (at least Talk) mostly uses esm by default.

• It wasn't a problem in v0.10.0 before migrating to Vite, because previously it was built to esm.
• It wasn't a problem with @nextcloud/webpack-vue-config v5.4.0. An old config just built an app with both esm and cjs vue copies in the bundle. But in v5.5.0 there was added resolve alias for vue. It results with using only one Vue package in the built and helps to get rid of multiple Vue on the page. At the same time, it broke building an app with this library, providing wrong Vue module type.

This PR:

1. Adds esm to build targets
2. Adds exports field to package.json providing proper entrypoint to each module type
3. Adds module field to package.json as a fallback for all tools not supporting exports
4. Removed library field from package.json (I have found no mentions about this field. Neither in npm docs, nor in nodejs or webpack/vite docs...
5. Removed global settings from rollup config. It is not required if we don't built iife / umd with global Vue.
6. Moved vue from dependencies to peerDependencies as it is a peer by design.
7. Removed @nextcloud/vue duplication from peerDependencies.

Related: nextcloud/spreed#9236

[ShGKme]

Also checked, that there is no problems on server build (on master).