Avoid transient ByteBufferView

Motivation:

When attempting to locate a single byte, creating a transient
ByteBufferView is an excessively heavyweight operation compared to a
simple getInteger. In particular, a BBV requires retain/release
operations to enforce the CoW invariants, as well as requires jumps
through substantial amounts of generic Collection code. While this can
be specialized, so can getInteger, and getInteger has much less code in
the way to cause costs.

Modifications:

- Replace temporary view creation with getInteger.

Results:

5% performance improvement on raw throughput tests.

Author: Lukasa

Sources/RediStack/RESP/RESPTranslator.swift

@@ -216,7 +216,7 @@ extension RESPTranslator {
 
         // sanity check that the declared content size matches the actual size.
         guard
-            buffer.viewBytes(at: buffer.readerIndex + expectedRemainingMessageSize - 1, length: 1)?.first == .newline
+            buffer.getInteger(at: buffer.readerIndex + expectedRemainingMessageSize - 1, as: UInt8.self) == .newline
         else { throw ParsingError.bulkStringSizeMismatch }
 
         // empty content bulk strings are different from null, and represented as .bulkString(nil)