Document that an input mapping creates a local variable scope

[falko]

The docs say:

If one or more output mappings are defined, the job/message variables are set as local variables in the scope where the mapping is defined. Then, the output mappings are applied to the variables and create new variables in this scope. The new variables are merged into the parent scope. If there is no mapping for a job/message variable, the variable is not merged.

https://github.com/camunda-cloud/camunda-cloud-documentation/blob/1f49a6c62cec5142815568b483519b439edb6fec/docs/components/concepts/variables.md?plain=1#L117

Does the creation of an input mapping also lead to hiding variables created by workers similar to an output mapping?

[falko]

We just discussed this in today's Camunda Cloud Family Get-Together and the answer is yes.

We agreed that it would make sense to improve documentation and maybe even add a hint in the Modeler to avoid people losing time figuring out the behavior.

[falko]

This issue has been raised by an Enterprise customer in SUPPORT-11857 and @ikheraj17 and I also stumbled over it when migrating a CP project to CC.