Publishing to environment also publishes to environment selected in Run & Debug section

Please include the following with each issue:

1. Describe the bug
When publishing to an environment a second publish will happen after the first publish succeeds/fails to publish.
The second environment published is always the environment selected in the Run And Debug section.

2. To Reproduce
Steps to reproduce the behavior:

1. Create a new extension with AL Go
2. Add 2 environments to the launch.json
3. Select one of these two environments to the Run And Debug section
4. Proceed to publish to the environment not selected in Run And Debug

3. Expected behavior
The initial publish executes and fails or succeeds but then stops there.

4. Actual behavior
After the first publish fails or succeeds VSC starts publishing to the environment selected in Run And Debug.
(See attached video)

5. Versions:
Pre-release version (17.0.1825603)

• AL Language: Yes
• Visual Studio Code: Yes
• Business Central: Yes
• Operating System:
  • [X ] Windows
  • Linux
  • MacOS

https://github.com/user-attachments/assets/4dba0416-64fe-47a6-a78d-91155550061c

Internal work item: AB#610060

Start by reproducing the publish flow in a new AL Go extension with two environments in launch.json, selecting one environment for Run and Debug and publishing to the other. No source files or tests are named, so trace the VS Code extension's publish entry point and identify why the selected debug environment is published again; done means only the requested environment is published once.