Refactor name validation: remove numeric check and simplify character validation

[YOMAN1792]

Description

This PR refactors the name validation logic by removing the redundant numeric check and simplifying the character validation to handle various character sets like Latin, Greek, Cyrillic, Hebrew, Arabic, and CJK. This change improves the validation process and ensures that only valid characters are accepted, making it more flexible for different language users within the community.

---

Motivation

The previous validation logic had a redundant numeric check, which was unnecessary because it was already covered by the new character validation logic. This update simplifies the code, improving code readability and making the validation process more flexible. It better supports a wider range of languages and scripts, which is an important step toward making the framework more inclusive for a global community.

---

Implementation Details

• The 'checkValidCharacter()' function is now responsible for validating characters based on their Unicode code ranges, including Latin, Greek, Cyrillic, Hebrew, Arabic, and CJK characters.

• The numeric check has been removed as it was redundant.

• The 'checkNameFormat()' function now solely depends on 'checkValidCharacter()' to validate names.

• This change is also a step toward ensuring that the ESX framework continues to grow in a way that is inclusive and beneficial for developers around the world.

---

Usage Example

The following function validates a name:

local function checkNameFormat(name)
    if checkValidCharacter(name) then
        local stringLength = string.len(name)
        return stringLength > 0 and stringLength < Config.MaxNameLength
    end

    return false
end

---

PR Checklist

• My commit messages and PR title follow the Conventional Commits standard.
• My changes have been tested locally and function as expected.
• My PR does not introduce any breaking changes.
• I have provided a clear explanation of what my PR does, including the reasoning behind the changes and any relevant context.

[Zykem]

Do early returns.

[Zykem]

Move the function checkValidCharacter to an ESX core function named ESX.IsValidLocaleString.

Do not check all character ranges globally. Instead, determine the character range based on the user's selected locale from the config.

For example, if the locale is set to zh-cn, validate only Chinese characters. Do not check for Russian, Arabic, or other unrelated character sets.

However, the following character ranges must always be allowed regardless of the selected locale:

• Basic Latin uppercase (A–Z)
• Basic Latin lowercase (a–z)
• Space and dash ( , -)
• Latin Extended

[Zykem]

Check single comments.

[Zykem]

LGTM

[Zykem]

LGTM, Thanks!

[Zykem]

Documentation update regarding your Pull Request.
esx-framework/esx-legacy-documentation@f0dd53e