Added NBT type

[LiteApplication]

The NBT class has the following capabilities

• Reading from Buffer object
• Writing to Buffer object
• Converting from/to python objects

100% test coverage for the nbt.py, Pyright and Ruff are happy

[ItsDrike]

Hi, thanks for the contribution! Just make sure to add a changelog fragment file (see changes/README.md) and it seems that you're failing unit-tests CI on windows, due to ValueError: the environment variable is longer than 32767 characters. Once that's addressed, I will give this a more thorough look.

Btw, you can ignore the readthedocs check failing, it shouldn't be related to this PR.
Edit: the readthedocs issue was fixed in #258, you can update this (rebase/merge main branch) to pass the CI.

[LiteApplication]

The issue has been addressed, all the tests pass on all the platforms.

[ItsDrike]

Note: I haven't yet checked the unit-test implementation at all, and this is more of a preliminary review, I haven't taken a deeper look at all of the logic and how things interract, but I wanted to submit it already since there's a fair few things I've noticed,

it's mostly minor fixes / standardization (surprised some of these weren't caught by the linter rules, I might need to take a look at that). But there are some more of a question based comments, where I'd like some feedback on how you meant for something to work, or on some code design choices.

PS: I know I'm a bit too pedantic, that's just how I am.

[ItsDrike]

Note: this will need rebasing, as #131 introduced an additional pyright rule, which your current code is almost certainly in violation of, also pyright was (finally) updated in #264. Additionally #274 has dropped the use of black and isort in favor of ruff, and ruff was also updated to a much more recent version.

That all very likely means that you will need to do some extra work to pass validation worfklow after rebase.

[ItsDrike]

Another quick one, just some more things I've noticed.

[ItsDrike]

LGTM!

There are still some minor details that could probably be changed, but I don't want to block this with insisting on those. That can always be done later. Generally, the implementation looks good to me. Thanks!