Binary RPC REPE

[stephenberry]

This is implementation of the new REPE binary RPC specification using BEVE

[stephenberry]

@jbbjarnason, I added a unit test that doesn't build yet, but I'll keep adding to it to describe the kind of interface we want.

I'm thinking of adding custom data as a std::vector<std::byte> to the header. This will require a double parse for the header, but I think this makes sense. The double parse allows users to parse the header knowing exactly what it should look like every time. And, it makes it more efficient to skip.

The message itself is still templated on the body, so you can decode/encode straight to memory.

[jbbjarnason]

looking good

[jbbjarnason]

Should the error be something else than bool?
How does this member relate to the error struct below

[jbbjarnason]

Can read_binary return an error with partial as an error code? In terms of networking, so we would know to async_receive more data into the buffer before trying again.

Secondly would it be beneficial to be able to only read the header?

glz::repe::header header{};
glz::read_binary(header, buffer);