Story: As a repository viewer, organization viewer, or superuser, I want to be able to use a regular expression to search so that I can effectively filter among a vast set of tags, repositories, or organizations or validate a regular expression pattern live for creating automation.

Background: A registry may possess a vast amount of content, typically as a result of automated ingest. Users should be able to search this content at all levels effectively. This has also been voiced as user-feedback to the new UI.

Acceptance criteria:

• optionally offer users a modifier to interpret their search string as a regular expression
• support this in the org list view, repo list view and tag list view
• in absence of the new APIs and for security reasons (redos attacks) the search should be carried out entirely on the client side