add fix for cfn-response code for nodejs custome resource

[pinzon]

Motivation

Custom resource models backed by nodejs lambda are experiencing deployment issues as a result of the nodejs cfn-response file containing an additional line ending character within the container, and the request is directing traffic to port 443.

Changes

• convert standard string to raw string to avoid extra \n character in the container code
• the request for the insertion of the resource deployment into the bucket uses url port not directly 443

Testing

The custom resource are not able to be deployed on this project so there is no need for a test

[github-actions]

LocalStack Community integration with Pro

    2 files  ±0      2 suites  ±0   1h 28m 35s ⏱️ + 1m 11s
2 692 tests  - 1  2 436 ✅  - 1  256 💤 ±0  0 ❌ ±0 
2 694 runs   - 1  2 436 ✅  - 1  258 💤 ±0  0 ❌ ±0 

Results for commit a33b3a6. ± Comparison against base commit 87f747f.

This pull request removes 2 and adds 1 tests. Note that renamed tests count towards both.

tests.aws.services.s3.test_s3.TestS3PresignedUrl ‑ test_s3_get_response_case_sensitive_headers[False]
tests.aws.services.s3.test_s3.TestS3PresignedUrl ‑ test_s3_get_response_case_sensitive_headers[True]

tests.aws.services.s3.test_s3.TestS3PresignedUrl ‑ test_s3_get_response_case_sensitive_headers

♻️ This comment has been updated with latest results.

[coveralls]

coverage: 83.408% (-2.5%) from 85.881%
when pulling a33b3a6 on lambda/patch/cfn-response-raw
into 87f747f on master.

[dominikschubert]

LGTM, in terms of testing this is actually covered in -ext. I think currently we only cover the python one, but we should extend this to have both a python-based as well as a NodeJS based custom resource test 👍

[dominikschubert]

by default localstack/localstack-pro will actually use 443 but that should be fine as it extracts it from the url anyway now 👍