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_

Inizia confrontando la pagina collegata delle storie di successo con le pagine separate di Briefcase e Toga, quindi esamina come il sito web principale organizza contenuti simili. Il lavoro sarà completato quando esisterà una pagina delle storie di successo combinata e coerente, con link alle app, descrizioni, piattaforme, screenshot dove appropriato e componenti BeeWare, collegata da entrambe le aree della documentazione.

Scritto dal modello di indicizzazione a partire dal testo della issue.