Fix missing DEBUG_PORT environment variable in Node.JS stack

[rm3l]

What does this PR do?:

This adds the missing DEBUG_PORT environment variable to the Node.JS stack. Otherwise, the debug command won't start when used with the starter project declared in this stack.
See devfile/api#929 for more details.

Which issue(s) this PR fixes:

Fixes devfile/api#929

PR acceptance criteria:

• Contributing guide
  Have you read the devfile registry contributing guide and followed its instructions?
• Test automation
  Does this repository's tests pass with your changes?
• Documentation
  Does any documentation need to be updated with your changes?
• Check Tools Provider
  Have you tested the changes with existing tools, i.e. Odo, Che, Console? (See devfile registry contributing guide on how to test changes)

How to test changes / Special notes to the reviewer:

I manually ran the tests/test.sh script (using odo 2.5.1) against both Minikube and OpenShift clusters.

[openshift-ci]

Hi @rm3l. Thanks for your PR.

I'm waiting for a devfile member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[rm3l]

Any idea why the ci/prow/v4.7-registry-test check is not passing? I keep seeing this in the logs, but can't figure out why:

ERRO[2022-09-14T17:16:35Z] Some steps failed:                           
ERRO[2022-09-14T17:16:35Z] 
  * could not run steps: step registry-test failed: "registry-test" test steps failed: "registry-test" pod "registry-test-registry-test-steps" failed: the pod ci-op-j5cqcxvj/registry-test-registry-test-steps failed after 9s (failed containers: test): ContainerFailed one or more containers exited
Container test exited with code 1, reason Error

[johnmcollier]

/retest

[rm3l]

Had to rebase and force-push to check this PR against the new tests introduced in #102

[christoph-jerolimov]

This is a "stack" and a Devfile 2.1, so from ODC side we don't support this so I can not help with a review here, right?

/uncc

[johnmcollier]

/retest

[johnmcollier]

/ok-to-test

[openshift-ci]

@rm3l: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/v4.7-registry-test	ff99678	link	true	/test v4.7-registry-test

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[johnmcollier]

/retest

[elsony]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BethGriggs, elsony, rm3l

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• stacks/OWNERS [elsony]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment