When using node next / node16 module resolution (`exports` field),
then Typescript will no longer check `types` field in package json but
use `types` from the `exports` field that is currently being used.

Signed-off-by: Ferdinand Thiessen <[email protected]>

For e.g. SabreDAV collection is only set, meaning its type after parsing
by the XML parser will be `string` and its value will be just the empty string.

Signed-off-by: Ferdinand Thiessen <[email protected]>

In case e.g. a directory is called `1` the XML parser will convert
the display name to a number. This is against the types and not expected behavior.

Signed-off-by: Ferdinand Thiessen <[email protected]>

fix(types): `resourcetype` can have any type, so can `collection`

fix: also export types for node next module resolution

fix(dav): The `displayname` prop should always be a string

As per RFC the value shall be octets representing the quota,
in all cases I know the value will be parsed to `number` by the XML parser.
(tested e.g. with Sabre / Nextcloud).

Signed-off-by: Ferdinand Thiessen <[email protected]>

fix(types): correct types for quota bytes

Update dependencies