[Fix] Correct Reporting of CTF Compressed Payload in Metadata

[MichaelLettrich]

The reporting of the CTF compressed payload size by the Metadata class is wrong.
Metadata stores the sizes of the encoded data, dictionaries, and the size of incompressible symbols in multiples of the word size of the underlying storage buffer. To get to bytes, the member function Metadata::getCompressedSize() multiplies DictWords + nDataWords + nLiteralWords by streamSize. streamSize on most occasions will not match the word size of the storage buffer, resulting in wrong reporting of the byte size for the compressed payload.

This fix:

• returns words by Metadata::getCompressedSize()
• converts word output into bytes wherever byte output is expected.
• Improves documentation in the Metadata class

[github-actions]

REQUEST FOR PRODUCTION RELEASES:
To request your PR to be included in production software, please add the corresponding labels called "async-" to your PR. Add the labels directly (if you have the permissions) or add a comment of the form (note that labels are separated by a ",")

+async-label <label1>, <label2>, !<label3> ...

This will add <label1> and <label2> and removes <label3>.

The following labels are available
async-2023-pbpb-apass4
async-2023-pp-apass4
async-2024-pp-apass1
async-2022-pp-apass7
async-2024-pp-cpass0
async-2024-PbPb-apass1
async-2024-ppRef-apass1
async-2024-PbPb-apass2
async-2023-PbPb-apass5