Align quick start deployment with Operaton

[hauptmedia]

Summary

• remove the Operaton Cloud reference from the quick start deployment note
• align the quick start modeling and deployment instructions with Operaton Modeler instead of Camunda Modeler
• remove outdated Camunda Modeler blog links from the quick start deployment step
• preserve the old deployment heading anchor with a hidden id so existing links keep resolving
• use local documentation links for Quick Start references to the Operaton docs
• replace the quick start worker follow-up URLs that returned 404 with the existing next tutorial page and fix the JavaScript worker snippet
• align the quick start Java worker prerequisite and compiler settings with Java 17 and polish the updated Modeler/deployment instructions

Verification

• rg -n "JDK 11|maven\\.compiler\\.(source|target)>11|opening up Operaton Modeler|Your pom\\.xml file of your project|right clicking|POST Request|JSON Body|Move onto|larger or equal|process then|In order to retrieve|Decision Table, click on|Deployment Name|hit the Deploy|Process Instances|Process Instance will|Decision Instances" docs/get-started/quick-start/decision-automation.md docs/get-started/quick-start/deploy.md docs/get-started/quick-start/gateway.md docs/get-started/quick-start/service-task.md -S returns no matches
• rg -n "JDK 17|maven\\.compiler\\.(source|target)>17" docs/get-started/quick-start/service-task.md -S confirms the Java worker now uses Java 17
• rg -n "Camunda Modeler|Operaton Cloud|Camunda Cloud|blog\\.camunda|blog\\.operaton|camunda\\.com/download|downloads\\.camunda\\.cloud" docs/get-started/quick-start/index.md docs/get-started/quick-start/service-task.md docs/get-started/quick-start/user-task.md docs/get-started/quick-start/gateway.md docs/get-started/quick-start/decision-automation.md docs/get-started/quick-start/deploy.md -S finds no matches
• rg -n "use-the-camunda-modeler-to-deploy-the-process|Use the Operaton Modeler" docs/get-started/quick-start/deploy.md -S confirms the compatibility anchor and new heading are present
• rg -n "https://docs\\.operaton\\.org/docs/documentation" docs/get-started/quick-start/service-task.md docs/get-started/quick-start/gateway.md docs/get-started/quick-start/decision-automation.md -S finds no matches
• rg -n -e 'https://docs\\.operaton\\.org/get-started/quick-start/(complete|success)' -e 'docs\\.operaton\\.org/get-started/quick-start' -e 'susbscribe' -e 'amount of ```' docs/get-started/quick-start/service-task.md -S finds no matches
• curl -I -L --max-time 20 https://docs.operaton.org/docs/get-started/quick-start/user-task/ returns HTTP 200
• git diff --check
• npm run typecheck
• npm run build succeeds; it reports the known pre-existing Docusaurus link/anchor warnings that are handled separately in Fix docs link checks and enforce quality gates #115

[kthoms]

This is wrong. Should be Camunda 7, or point to the Operaton Modeler already?

[hauptmedia]

Addressed in the current branch: the note now refers to Operaton Modeler and setting the execution platform to Operaton Platform before deploying to Operaton.