[DOC] Regex docs

[itaismith]

Description of changes

Adding regex ops to docs

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[propel-code-bot]

This PR updates the documentation to include details and examples for the new $regex and $not_regex operators available in full text search filtering. The sidebar navigation is also updated to reflect the expanded content with the new page title 'Full Text Search and Regex'.

This summary was automatically generated by @propel-code-bot

[propel-code-bot]

[Documentation]

Consider adding an example of the $not_regex operator similar to how you've shown both $contains and $not_contains. This would provide complete documentation for the regex filtering capabilities.

[propel-code-bot]

[BestPractice]

Consider adding a simpler regex example alongside the email pattern. Email regex patterns are quite complex, and a simpler example like case-insensitive matching might be more approachable for users new to regular expressions.