refactor(dap): ensure run_last fetches the latest configuration by name

The current implementation of run_last caches the configuration object from the previous session. This leads to "stale" runs if the user modifies their launch.json or if a dynamic configuration provider updates its values (e.g., changing an environment variable from "RUN_MODE": "a" to "b"). Example Case: When debugging a Python module with a launch.json like this: ```json { "version": "0.2.0", "configurations": [ { "name": "main", "type": "debugpy", "request": "launch", "module": "mobile.main", "env": { "RUN_MODE": "a", } } } ``` If the user changes "RUN_MODE" to "b", the updated run_last will correctly pick up the new environment variable without requiring the user to re-select the configuration manually.