Add Order Fulfillment Workflow and Workflow Saga demo apps

[schananas]

Summary

Two new demo modules showing how to model multi-step business processes with the Axon Workflow Engine:

• order-fulfillment-workflow — order → reserve stock → payment → ship → notify. Includes a live tracking UI: Leaflet map with animated truck movement, status pills, stats panel and activity log, all driven by SSE pushed from the projection's @EventHandlers. One-click buttons trigger single orders, bursts, and failure scenarios (out-of-stock, payment-timeout).
• workflow-saga — saga-style order process showing wait/compensate patterns with the workflow DSL.

Test plan

• mvn verify in order-fulfillment-workflow/ (Testcontainers IT spins up Axon Server)
• mvn verify in workflow-saga/
• Manual: mvn spring-boot:run in order-fulfillment-workflow/, open http://localhost:9090/, click "Stress test ×25" and "Mixed burst" — markers should animate end-to-end on the map

[smcvb]

Suggested change

	<axon-workflow.version>1.0.0-SNAPSHOT</axon-workflow.version>
	<axon-workflow.version>0.1.0</axon-workflow.version>

[smcvb]

Suggested change

	- The Axon Workflow Engine (`io.axoniq.framework.workflow:*:1.0.0-SNAPSHOT`) installed in the local Maven repository
	- The Axoniq Workflow Engine (`io.axoniq.framework.workflow:*:1.0.0-SNAPSHOT`) installed in the local Maven repository

[smcvb]

I'd word this section differently. It's fine to suggest things are better, but stating it like this is super on-the-nose and not in all cases entirely correct. It would come across as more honest if you also include what's better in a Saga compared to Workflows (from my pov, the massive single-method block is a massive no-no, for example).

[smcvb]

All seems fair to me, but I'd want @zambrovski to give his two cents as well before merging.

Furthermore, although it's great this is here, we have not yet updates the code-samples build with AF5 at all. So, it might be a bit early to have these modules already.

[zambrovski]

ObjectMapper can do it much faster by transforming a bean to Map<String, Object>.

[zambrovski]

I believe this has its own value to be presented here, independent of the visibility of examples we provide inside the module itself. This is a show case and it lives along side with other show cases.

Given the workflow-module is not public yet, I believe this one can be public before the access to the extension repository is changed to public.

So to me, if the proposed changes are applied, I see a value in publishing it here, in order to be able to show it to public already.