feat: uptake atserver_message & reduce redundant memory reallocations

[XavierChanth]

• Switch to static memory allocations where it makes sense
• I made some mistakes in telling the team to use heap memory in place where it wasn't necessary to.

[XavierChanth]

See also #466

[XavierChanth]

So I think there's a fundamental problem with the way the connection layer provides memory back to the application.

We currently have to:

• allocate memory to read from mbedtls
• then allocate again to pass the memory into the application layer with the parts of the message we don't want stripped out.
• then whatever allocations happen to consume that message further.

Instead, we should try to allocate that message once, and use indices and carefully replace delimiters with null terminators.

For example to consume the message:

struct message {
  unsigned char* buffer;
  uint32_t buffer_len; // length of the entire buffer
  uint32_t payload_idx; // index of the actual payload contents
}

This struct is much more efficient to pass around, and other structs can consume it, copying just the indices rather than the whole buffer contents.

Buffer is still a pointer to the start of memory allocation, so it can still be used to free at the end.

To get the actual payload contents for example, the address for it would be buffer + payload_idx.

[XavierChanth]

added the atserver_message struct a while back, connection and it's callers need to implement it as the interface for server responses instead of buffer and length.