Merge /search and /browse views

### Describe the problem

(I wrote things below during my debugging, but I can't no longer reproduce it, although the point stands)

When you're inside Component > Search, the Search button gets you to the translation UI, which is rather useful if you want to review suggestions and some such.
If you're inside the global project-wide Search, the search button gets to a bit of a confusing search UI, with no obvious way to list units from there.

We have quite a few components, but even if it were two components, such behaviour is unfortunate.

I tried to look at the code (or well, at HTML mostly, cause I couldn't understand where SearchForm gets its URL) and the difference between the component's search URL and the global search URL is that the component's search URL leads to links like `https://translate.codeberg.org/translate/PROJECT/COMPONENT/LANG/?q=` and project-wide search leads to, well, search.

### Solution brainstorm

After some reverse-engineering, I came up with `https://translate.codeberg.org/translate/veloren/-/LANG/?q=`, which does exactly what I want.
By skipping the component with `-` and specifying only the language and the query string, I get quite a convenient process of reviewing all strings in the project (for example, if I want to onboard a new dedicated reviewer and I want to check their suggestions)

It would be nice if we could introduce this into UI in some way.
My first idea was to add two buttons to SearchForm with an alternative `formaction` for Translate, or I guess we could add such a link to "filtered by query list" page, though `formaction` way would be preferable.

### Describe alternatives you have considered

well, I've added that magic URL to our docs, and that's what I use for now

actually, maybe instead of project-wide search, we could start with language-wide search?

### Screenshots

Now

Expected

### Additional context

_No response_