Improve validation, handle empty options.phrases

[fityannugroho]

PR Checklist

Please check if your PR fulfills the following requirements:

Put [x] to check

• I have read the documentation.
• I have read and followed the Contributing Guidelines.
• I have included a pull request description of my changes.
• I have included the necessary changes to the documentation.
• I have added tests to cover my changes.

PR Type

What kind of change does this PR introduce?

Please check any kind of changes that applies to this PR using [x]

• Bug fix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• ..... (describe the other type)

What is the current behavior?

Please describe the current behavior that you are modifying, or link to a relevant issue.

Issue Number: N/A

• Crash when the options.phrases contains [, {, or ( item.

  Invalid regular expression: /\b[\b/: Unterminated character class
  

• Validation for options.charSets only about the character length.
• When options.phrases is [], the result is same with the text input (nothing changes).

What is the new behavior?

• Tighten validation for options.phrases by only allowing alphabets, numbers, spaces, and some symbols (-_'/).
• Tighten validation for options.charSets by only allowing alphabets for the key and prohibiting the use of control characters for the item of the value.
• Now, options.phrases with undefined and [] are same (will obscures the whole text).

Other information

None