Potential fix for code scanning alert no. 71: Incomplete string escaping or encoding

[kkartunov]

Potential fix for https://github.com/topcoder-platform/platform-ui/security/code-scanning/71

To fix this issue robustly:

• Use a well-tested escape function that escapes all special RegExp characters, including backslashes and whitespace, in a single step.
• If you must perform additional replacements (e.g., replace spaces in the normalized target string with a specific RegExp subpattern), do so before the call to escapeRegexLiteral, or do all escaping (for both standard RegExp metacharacters and for your application-specific substitutions) in a single regular expression.
• In this code, instead of first escaping all metacharacters and then replacing spaces, do it all at once: replace all contiguous (one or more) separator characters (e.g., spaces, underscores, hyphens) with a RegExp subpattern (like [-_\s]+), after escaping actual special characters, and ensure that no intermediate string manipulation reduces the escaping quality.

For this file specifically, edit the block constructing the RegExp.

• Refactor the phase name normalization and escaping to:
  • Replace all groups of spaces (or separators) with a constant placeholder (e.g., __WORDSEP__)
  • Escape the rest of the string (all RegExp metacharacters including backslashes)
  • Replace the placeholder with the target RegExp subpattern (e.g., [-_\s]+)

No new dependencies are required since the standard escaping function is already robust, but you may consider (if allowed) to use a trusted library like escape-string-regexp.

---

Suggested fixes powered by Copilot Autofix. Review carefully before merging.

[github-actions]

[⚠️ correctness]
The use of new RegExp(escapeRegexLiteral(WORDSEP_PLACEHOLDER), 'g') to replace the placeholder with the pattern [-_\\s]+ is correct, but consider verifying that WORDSEP_PLACEHOLDER is unique enough to avoid accidental matches in the input string. If WORDSEP_PLACEHOLDER could appear in the input, it might lead to incorrect replacements.

[kkartunov]

@copilot fix the lint as it fails doe to errors.

[Copilot]

@kkartunov I've opened a new pull request, #1378, to work on those changes. Once the pull request is ready, I'll request review from you.

[github-actions]

[💡 style]
Consider adding semicolons at the end of statements to maintain consistency with the rest of the codebase, which uses semicolons. This can help prevent potential issues with automatic semicolon insertion.

[github-actions]

[⚠️ correctness]
The replacement pattern [-_\s]+ is used to match sequences of separators. Ensure that this pattern aligns with the intended behavior and that no additional separators need to be considered. If the pattern should be more flexible, consider documenting the expected input format.