Splitting out `types` into libgemini?

[aThorp96]

Hello! I've been writing a small gemini client and I believe a lot of the functionality in the types directory could be used as a standalone library. Is that something that would be of interest at all?

[panicbit]

I haven't actively worked on this library in a while, so right now I can not judge wether this is reasonable or even useful, but I am open to the idea.

[panicbit]

I've had a look now and decided to try splitting the module into a separate crate.

[panicbit]

I'm not sure wether to publish this as northstar-types or gemini-types though.

[panicbit]

This also raises the question of how to do versioning. If I'd keep the types crate in this repository, it would be the easiest to manage, but it would also make it unclear how to tag releases.

[aThorp96]

One possibility would be to use features to either import the full package or just the gemini library. That would save some compile time on the end user's end without any operational overhead (I think) on the maintainers' end-- just the initial setup.