lz4: Update version from 1.8.2 to 1.8.3

[Release notes][1]:

> This is maintenance release, mainly triggered by issue #560.
>
> #560 is a data corruption that can only occur in v1.8.2, at level 9
> (only), for some "large enough" data blocks (> 64 KB), featuring a
> fairly specific data pattern, improbable enough that multiple cpu
> running various fuzzers non-stop during a period of several weeks where
> not able to find it. Big thanks to @Pashugan for finding and sharing a
> reproducible sample.
>
> Due to this fix, v1.8.3 is a recommended update.
>
> A few other minor features were already merged, and are therefore
> bundled in this release too.
>
> Should lz4 prove too slow, it's now possible to invoke --fast=# command,
> by @jennifermliu . This is equivalent to the acceleration parameter in
> the API, in which user forfeit some compression ratio for the benefit of
> better speed.
>
> The verbose CLI has been fixed, and now displays the real amount of time
> spent compressing (instead of cpu time). It also shows a new indicator,
> cpu load %, so that users can determine if the limiting factor was cpu
> or I/O bandwidth.
>
> Finally, an existing function, LZ4_decompress_safe_partial(), has been
> enhanced to make it possible to decompress only the beginning of an LZ4
> block, up to a specified number of bytes. Partial decoding can be useful
> to save CPU time and memory, when the objective is to extract a limited
> portion from a larger block.

[1]: https://github.com/lz4/lz4/releases/tag/v1.8.3

lz4.be0

@@ -1,6 +1,6 @@
 #!/usr/bin/env beesh
 
-# BEE_VERSION lz4-1.8.2-0
+# BEE_VERSION lz4-1.8.3-0
 
 ## this file was created by bee init and should be executed to build a
 ## bee-package. (Additional hints are located at the end of this file.)