Right now, there's not an easy way to archive VecDeques. When archived, they're functionally the same as Vec so we should be able to piggyback off the implementations for Vec.

• Archive impl should archive as ArchivedVec and use a VecResolver as its resolver.
• Serialize impl should serialize using [ArchivedVec::serialize_from_slice](https://docs.rs/rkyv/latest/rkyv/vec

Brief feature description

Since we have some CMake code to maintain, it make sense to enforce on this code also code quality rules like we do with the C++ code.

A possible tool-framework could be cmakelang which offers tooling for formatting and linting CMake Code properly.
Other suggestions are always welcome.

Detailed i

This is more of a meta issue, so contributors can expand docs and add it.

What docs are needed?

• API Docs. Easiest to add needed on most public methods
• How-To. Just a quick cookbook examples how to setup some Linguini in a specific case. No external dependencies needed.
• Tutorial??. Possibly needed, but Linguini is relatively simple.
• Onboarding docs for new contribut