Docs: Reference Handling of Custom Terminating Byte Sequences (#625)

### Motivation

See: apple/swift-openapi-runtime#115

### Modifications

This PR references the changes introduced by TODO in the documentation.

### Result

Users planning to generate code for OpenAPI specs with custom
terminating byte sequences will hopefully find it easier to make the
necessary changes in their code.

Please let me know if there are other places where these changes could
be mentioned.

### Test Plan
.

---------

Co-authored-by: Honza Dvorsky <[email protected]>

Sources/swift-openapi-generator/Documentation.docc/Articles/Useful-OpenAPI-patterns.md

@@ -113,8 +113,9 @@ The returned binary body contains the raw events, and the stream can be split up
     - encode: `AsyncSequence<some Encodable>.asEncodedJSONSequence(encoder:)`
 - Server-sent Events
     - decode (if data is JSON): `AsyncSequence<ArraySlice<UInt8>>.asDecodedServerSentEventsWithJSONData(of:decoder:)`
+    - decode (if data is JSON with a non-JSON terminating byte sequence): `AsyncSequence<ArraySlice<UInt8>>.asDecodedServerSentEventsWithJSONData(of:decoder:while:)`
     - encode (if data is JSON): `AsyncSequence<some Encodable>.asEncodedServerSentEventsWithJSONData(encoder:)`
-    - decode (for other data): `AsyncSequence<ArraySlice<UInt8>>.asDecodedServerSentEvents()`
+    - decode (for other data): `AsyncSequence<ArraySlice<UInt8>>.asDecodedServerSentEvents(while:)`
     - encode (for other data): `AsyncSequence<some Encodable>.asEncodedServerSentEvents()`
 
 See the `event-streams-*` client and server examples in <doc:Checking-out-an-example-project> to learn how to produce and consume these sequences.