Provide "jump ahead" variant in configurator to skip coding the early microservices

[holly-cummins]

@agoncal points out that for some of the advanced variations, like azure and kubernetes and extensions, workshop participants may not have interest (or time) in the REST API Java coding of the earlier sections of the workshop. We should provide an intermediate zip with those parts pre-built, and a workshop variation that starts with people downloading and building that zip.

[agoncal]

And in terms of documentation we should either have the existing Core chapters, or, a separate chapter that just goes "in the ZIP file you have 3 microservices (Villains, Heroes, Fight) and a UI, this is how you run the entire thing".

So, maybe a new guard (use-core) and if true then we leave the Villains, Heroes, Fight and UI chapters as they are, if false we introduce this new chapter about how to run the existing microservices

[agoncal]

BTW I've added this intermediate ZIP in #400. We now have 3 zip files:

• quarkus-super-heroes-workshop.zip: contains the bare minimum code to follow up the workshop
• quarkus-super-heroes-workshop-core.zip: contains all the code of the CORE (Fight, Villain, Hero, UI)
• quarkus-super-heroes-workshop-complete.zip: contains all the code