Correct the Documentation and Termnology for Character vs Byte Count on things like %LEFT

I would like to propose a refinement to the terminology used in the documentation for the third parameter of %LEFT, %RIGHT, and other RPG IV built-in functions that handle multi-byte characters. Currently, the terms NATURAL and STDCHARSIZE are used, but they can be ambiguous and do not clearly distinguish between character-based and byte-based operations.

To provide greater clarity and consistency with industry-standard terminology used in C/C++, I recommend updating the terminology as follows:

• BYTECOUNT (currently referred to as STDCHARSIZE)
• Specifies the number of bytes being processed, without regard for character boundaries.
• In single-byte character sets (e.g., EBCDIC), BYTECOUNT and CHARCOUNT return the same value.
• In multi-byte character sets (e.g., UTF-8), BYTECOUNT may reference partial characters, leading to truncation if not carefully managed.
• CHARCOUNT (currently referred to as NATURAL)
• Specifies the number of characters being processed, regardless of how many bytes each character occupies.
• Ensures operations respect full character boundaries in variable-width encoding schemes like UTF-8 or UCS-2.

Why This Change Matters

By using BYTECOUNT and CHARCOUNT, the documentation would more clearly communicate the behavior of these modes and avoid confusion, especially when working with UTF-8 and other multi-byte CCSIDs. Additionally, this terminology aligns with how C and C++ handle similar distinctions, making it easier for developers with experience in those languages to understand RPG IV string operations.