Please address the comments from this code review:
## Overall Comments
- Instead of regex on the search string, consider using URLSearchParams to parse and compare decoded parameter values for more robust handling.
- Add unit tests for the new containsPatternIgnoringEncoding util to cover edge cases like special characters or multiple parameters.
- Escape the pattern or avoid interpolating arbitrary strings into the RegExp to prevent unintended regex behavior when pattern contains special characters.

## Individual Comments

### Comment 1
<location> `ui/apps/platform/src/Containers/MainPage/Navigation/HorizontalSubnav.tsx:35` </location>
<code_context>

 import './HorizontalSubnav.css';

+// Check if the search string contains the pattern or the encoded version of the pattern
+function containsPatternIgnoringEncoding(search: string, pattern: string) {
+    return new RegExp(`${pattern}|${encodeURI(pattern)}`, 'i').test(search);
+}
</code_context>

<issue_to_address>
The regex in containsPatternIgnoringEncoding may match unintended substrings.

Matching with the current regex may cause false positives if the pattern appears within another parameter or value. Parsing the query string and comparing parameter values directly would provide more accurate results.
</issue_to_address>