Add more deployments targets to the workshop

Today the workshop uses several frameworks (Quarkus, SpringBoot and Micronaut) and several artifact formats (JVM and GraalVM binary). We should also have several deployment target. Today we only deploy on ACA, but it would be nice to deploy on AppService and Azure Function.

The structure of the workshop could change around:

* Setting up the project
* Developing the applications
* Developing the Quarkus Application
* Developing the Micronaut Application
* Developing the SpringBoot Application
* Executing, Load Testing and Monitoring Locally
* Deploying, Load Testing and Monitoring on ACA
* Deploying, Load Testing and Monitoring on AppServices
* Deploying, Load Testing and Monitoring on Azure Function

The "Going Native" should go under the "Developing the applications" for each app

No files or tests are named. Start by locating the workshop sections for setting up, developing, local execution, and ACA deployment, then review how the Quarkus, Micronaut, and SpringBoot examples are organized. Done means the workshop also documents AppService and Azure Function deployment, with the proposed section structure and “Going Native” placement reflected.

Written by the indexing model from the issue text.