✨ Support updating values during execution

What's the problem this feature will solve?

Typical debuggers often allow users to set the values of variables during execution. Having a similar feature for this in the MQT Debugger would be interesting.

This new feature should also be added to the DAP

Describe the solution you'd like

This comes in two forms:

• Setting classical values: Updating classical variables allows the developers to change classical values that are used in classically-controlled gates to check the behavior of the program. Considerations: Often, classical values represent the quantum state in some way (think of quantum teleportation as one use case). Simply changing the values may break many algorithms, so it's not necessarily always usful.
• Setting qubit values: Updating qubits could be helpful for debugging. Users may either want to update individual qubits or sets of multiple qubits. Considerations: If updated qubits were entangled with other qubits, this could cause issues. One should first consider how to best solve this situation.

Start by mapping the MQT Debugger's execution and variable-inspection entry points, then identify the DAP integration points mentioned in the issue. Clarify how classical values, individual qubits, multiple qubits, and entangled qubits should be handled before implementation. Done means the behavior is defined and supported consistently in both the debugger and DAP.