PAW Workbench search functionality is limited: multiple extensions that will help users on a day to day basis

When using the PAW Workbench Search functionality there are 2 options: search for text in code of processes and rules, and search for text in object names.

It seems that for both options there is a fixed and hardcoded limit of 60 search results. The means that searching for a term like 'Revenue' in the code of processes and rules, will only list 620 hits. While this may seem a lot, it is often not enough. But the main problem is that we can never get to search results 61 to ... in case of more than 60 results. Therefore, 1 idea could be pagination such that also these other results can be accessed. Come to think about it, I would like to ask for a number of improvements in this area:

- Count and display the total number of search results, and the number of files in which hits were found. This means that let's say 3 hits of search results in the same rule or process file, that it counts as 3 and a total count of 1 for the "file count". These are 2 different things and useful information.

- Search with regular expressions (whereby other areas already support search with regex, thanks for that !)

- The possibility to hide a search result from the list of results. What always happens is that there are, say, 15 results. This means 15 places in code where a change needs to be made. Then we proceed by going one after the other in the list, but the list always contains 15 results. The list will not automatically shrink with the items that are already dealt with. This is confusing since the list is not like a list where we "check" each item that was processed. An option to hide from the results list could be useful.

- A find/replace option that is applied to all 15 results for the previous example above (and regex with \1, \2, ... in the "replace with" field would be awesome). Imagine that the model contains many times the word "Initalise" but we prefer "Initialize" with z. A manual find/replace is tedious.

- In the case of multiple TM1 models, the search will often default to the first TM1 server, when I would not expect it to change. For instance, just switch between "Search names" and "Search code" when either TM1 model is selected.

- Search through elements and their aliases? That would be useful and much more useful than being able to search for the name of a view, to name just 1 thing. I hardly ever want to search for a view name or subset name and if I would like to search for it, I would want to do it with a regex since view and subsets contain a timestamp or random number and so I want to search for those objects with 10 digits like:  \d{10}

In the end, all of these things are possible with for instance Notepad++ or VSCode towards the RUX and PRO files. We go backwards in useability by using PAW instead of Notepad++ and with V12 not file based this becomes more difficult too. Hence the need for a real, performant, PAW search in Workbenches. Not to mention search in a book, all books in a folder, etc.....