Fix code scanning alert no. 27: Inefficient regular expression

[kdinev]

Fixes https://github.com/IgniteUI/ignite-ui/security/code-scanning/27

To fix the problem, we need to modify the regular expression to remove the ambiguity that causes exponential backtracking. Specifically, we can replace the ambiguous character class [\w\$\-]+ with a more precise pattern that avoids backtracking issues. One approach is to use a non-capturing group with a negated character class to ensure that the pattern matches in a linear time complexity.

• General Fix: Modify the regular expression to use a non-capturing group with a negated character class to avoid backtracking.
• Detailed Fix: Replace the pattern [\w\$\-]+ with (?:[^\s{}])+ to match one or more characters that are not whitespace, curly braces, or other problematic characters.
• File/Region/Lines to Change: The change should be made in the file src/js/modules/infragistics.templating.js on line 129.
• Required Changes: No additional methods, imports, or definitions are needed to implement this change.

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

[coveralls]

coverage: 84.637%. remained the same
when pulling c7b8043 on alert-autofix-27
into 63c065b on master.