Buffer::empty should not allocate

[gatesn]

Describe the bug

Currently Buffer::empty goes via BufferMut::empty, but this forces an allocation.

If we use Bytes::empty instead, then it refers to a static empty bytes slice. Alignment checks may fail.. which we'll need to figure out.

To Reproduce

No response

Expected behavior

No response

Additional context

No response