Move Success stories to website

### What is the problem or limitation you are having?

I started to proofread the [success stories](https://toga.readthedocs.io/en/stable/about/success.html), then I thought... Why not reformat this to make it more consistent and informative?

### Describe the solution you'd like

I'm envisioning a table, listing the same info for each app:

- Name (which links to the app, as currently)
- Perhaps a small screenshot
- Brief description of what it does
- Platform(s) supported

Also, we currently have one page for Briefcase and one for Toga; they have some apps in common and some unique, and there's no mechanism to sync these. Considering how often people ask about examples, I think it might make more sense to put one combined page on the main site, and potentially link to it from both docs. It would also then make sense, I imagine, to add a column for "BeeWare component(s) used".

### Describe alternatives you've considered

We could still maintain separate pages, but I'm not sure if there's a good way to make sure they stay in sync with each other. It's also not clear, currently, from just looking at one, which of the apps also use the other.

If we do keep the individual pages, it seems redundant to mention that each app uses the tech in question.

### Additional context

_No response_

Beginne damit, die verlinkte Seite mit Erfolgsgeschichten mit den separaten Seiten zu Briefcase und Toga zu vergleichen, und prüfe anschließend, wie die Hauptwebsite ähnliche Inhalte organisiert. Erledigt ist die Aufgabe, wenn es eine kombinierte, konsistente Seite mit Erfolgsgeschichten gibt, die App-Links, Beschreibungen, Plattformen, gegebenenfalls Screenshots und BeeWare-Komponenten enthält und von beiden Dokumentationsbereichen aus verlinkt ist.

Vom Indexierungsmodell aus dem Issue-Text verfasst.