feat: Add alternative methods, so Bytes is not required

[Norbiros]

Fixes: #17

This solution, while not perfect, enables full utilization of CrabNBT without needing to include bytes crate in your project.

In future, I'll redesign this to improve performance (writing directly to Vec instead of serializing bytes and then pushing it) and usability, but this will require changes to public methods and a new major version (see #18 for details).

[SzczurekYT]

So this just adds wrapper functions around current code which still use bytes right?

[SzczurekYT]

Do not call a Vec cursor, because it is not a cursor.

[Norbiros]

So this just adds wrapper functions around current code which still use bytes right?

Yes, it's fine to use bytes. The problem was that if you wanted to interact with those methods in CrabNBT, you had to add bytes to your project. Now you can use temporary wrapper functions. Probably even in v1.0.0 we'll use bytes under the hood.

[SzczurekYT]

but this will require changes to public methods and a new major version (see #18 for details).

No, that is wrong.
From semver spec

Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

Until we release 1.0.0 we are allowed to break public api if needed.

[Norbiros]

Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

Until we release 1.0.0 we are allowed to break public api if needed.

Have fun fixing breaking changes in minor updates. That is just frustrating, even if semver spec allows. Most of libraries that we use in CC are below 1.0.0 and CrabCraft will be until we achieve complete vanilla compatibility :3