WebClient: Single `miden-web-app`, multiple use cases

Currently, each tutorial mandates the user creates a new app (always called `miden-web-app`). This is annoying.

We should either:
1. Amend the instructions to create a different app name, or
2. Use a single app, with setup instructions part of #106. Then, add separate functions to invoke the different tutorial phases:
1. This could be done by adding more UI components (buttons) to trigger the different functions, or
2. Always keep one button, but replace the contents of `app/page.tsx`.

2.i. is a little more complex (e.g. we need to handle cases where tutorial `i-1` was skipped and the user jumped straight to `i`), so I suggest 2.ii should be done.

cc @partylikeits1983 @Dominik1999

The issue is about the miden-web-app in the tutorials repository. Start by examining the existing app structure, likely in `app/page.tsx` and related tutorial setup files. Understand how different tutorial phases are currently triggered. The goal is to modify the app to support multiple tutorials from a single instance, potentially by dynamically updating the page content. Check issue #106 for related setup instructions. 'Done' means a user can run all tutorials from one web app without creating new ones each time.

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