fix: node.js auto-configuration not supporting multiple projects

[AkibaAT]

The Problem/Issue/Bug:

Currently, the Node.js auto-configuration does nothing if it finds at least one configured interpreter. Additionally, it doesn't ensure that the available interpreters include one for the current DDEV project.

How this PR Solves the Problem:

Update the check to iterate over the available configurations, and verify that they include the expected docker-compose config for the current project.

Manual Testing Instructions:

• Make sure that no docker-compose remote interpreter is currently configured for node.js
• Open a DDEV project
• Verify that the config got added
• Open a second DDEV project
• Verify that an additional configuration got added

Related Issue Link(s):

[sonarqubecloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[rfay]

Thanks for working on this!