`decodeBuffered` APIs should all be configurable to throw the `EncodingSizeException`

[05nelsonm]

Having trouble squaring a circle in kmp-file whereby if a consumer writes text to a file which, when ran through decodeBuffered, the UTF-8 byte size exceeds Int.MAX_VALUE, they cannot then read the file because its size is greater than Int.MAX_VALUE.

There needs to be a parameter throwSizeException or something.

kmp-file and kmp-process are already using the 2 parameter decodeBufferedanddecodeBufferedAsyncfunctions from theSNAPSHOTpublication, so those should be duplicated and marked as deprecated until2.6.0` release is cut; a separate issue will be created to ensure that happens.

All functions should require the parameter be specified.