Investigate why node apps fail to build so often in e2e tests

[danail-branekov]

We get very frequent e2e failure because our sample apps fail to build:

 ===== Logs for pod "19363a91-178d-4464-87a9-ea331153909c-build-2-build-pod", container "build" =====
  Timer: Builder started at 2024-06-09T12:21:46Z
  
  Paketo Buildpack for CA Certificates 3.6.7
    https://github.com/paketo-buildpacks/ca-certificates
    Launch Helper: Contributing to layer
      Creating /layers/paketo-buildpacks_ca-certificates/helper/exec.d/ca-certificates-helper
  Paketo Buildpack for Node Engine 3.2.1
    Resolving Node Engine version
      Candidate version sources (in priority order):
                  -> ""
        <unknown> -> ""

      Selected Node Engine version (using ): 20.11.0

    Executing build process
      Installing Node Engine 20.11.0
  read tcp 10.92.0.191:53922->104.20.23.46:443: read: connection reset by peer
  Timer: Builder ran for 6.382677531s and ended at 2024-06-09T12:21:52Z
  ERROR: failed to build: exit status 1

The error above causes the test to eventually fail with

"errors": [
                      {
                        "detail": "Droplet not found. Ensure it exists and you have access to it.",
                        "title": "CF-ResourceNotFound",
                        "code": 10010
                      }
                    ]

Here is an example failure: https://ci.korifi.cf-app.com/teams/main/pipelines/main/jobs/run-e2es-periodic/builds/15789

While this is not a problem with Korifi, it is still pretty annoying. What is causing the connection reset? Should we switch to another sample app that does not involve nodejs?