fix: allow number and boolean values in validation message "$value" tokens

[kffl]

Description

As reported in issues #921 and #1046, the $value token in validation message isn't replaced properly in some cases. It turns out that the $value token is parsed as expected only when the provided value is of type string, which results in commonly used validators with non-string values such as @MinLength, @Min, @MaxLength, @Max ect. to leave the $value token in the validation message without replacing it. This PR relaxes the runtime typecheck performed when constructing the validation message by allowing types boolean and number (alongside string) to act as $value token replacements.

Checklist

• the pull request title describes what this PR does (not a vague title like Update index.md)
• the pull request targets the default branch of the repository (develop)
• the code follows the established code style of the repository
  • npm run prettier:check passes
  • npm run lint:check passes
• tests are added for the changes I made (if any source code was modified)
• documentation added or updated
• I have run the project locally and verified that there are no errors

Fixes

references #1046, references #921

[NoNameProvided]

Hi @kffl, can you please rebase or cherry pick this to the latest develop branch?

Edit: I have done if for you.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.