Improve search framework

[jonasraoni]

Problems:

• Accuracy: The more data we add, the higher the probability of having results being missed.
• Performance: Might lead to load spikes at the server.
• Storage: Consumes lots of space in the database.
• Slow to index: solved by tasks and improved by https://github.com/pkp/pkp-lib/issues/8915
• Maintenance: There's a lot of code to support the search.

Related issues:

• https://github.com/pkp/pkp-lib/discussions/7968
• https://github.com/pkp/pkp-lib/issues/8915
• https://github.com/pkp/pkp-lib/issues/8522
• https://github.com/pkp/pkp-lib/issues/7140
• https://github.com/pkp/pkp-lib/issues/9829
• Not filed, but could become a memory hog on a large installation that makes use of workers: https://github.com/pkp/pkp-lib/blob/dcf2f9a1cbb7bd131f4eecc934c078be0110e263/classes/search/SubmissionSearchDAO.php#L82

Even after an improvement attempt at the search, the problems still persist on larger installations: https://forum.pkp.sfu.ca/t/3-4-0-3-large-sql-queries-slowing-down-site/81674 https://forum.pkp.sfu.ca/t/ojs-3-4-0-4-performance-issue-ojs-3-3-0-14-to-ojs-3-4-0-4/83655

[diegoabadan]

Hello!

To our knowledge, an institution with the recently released OJS 3.4.0-7 and which hosts several journals was experiencing immense slowness and contacted us. We had to apply this fix: https://forum.pkp.sfu.ca/t/ojs-3-4-0-4-performance-issue-ojs-3-3-0-14-to-ojs-3-4-0-4/83655/5?u=abadan