create-daml-app: make tests pass on m1

[garyverhaegen-da]

This is very much a "just make it work" type of patch. The main issues were:

• A bunch of type errors in the index.test.ts file when opened in VS Code. I'm not sure how it happened, but it's possible I'm just using a more recent TS compiler than whoever edited this last.
• localhost, on my machine at least, resolves to ::1, and therefore the connections were just not established. I've opted for replacing localhost with explicit 127.0.0.1.
• npm-cli.js was not an executable in my PATH.

Those tests are obviously not tested by CI, so please review carefully / test this on your own machine before approving.

CHANGELOG_BEGIN
CHANGELOG_END

[remyhaemmerle-da]

look reasonable.

[garyverhaegen-da]

Additional testing steps taken:

• Build daml-sdk-head on this branch.
• Create a new project with daml-head new myproject --template=create-daml-app to get a new project using the updated config.ts file.
• Manually change the version strings from 0.0.0 to 2.3.4 in both daml.yaml and ui/package.json. We don't actually care all that much about the daml ones here, but consistency is nice, and we need a "real", published version number for npm to pick up.
• Manually follow the "Your First Feature" instructions.
• Run daml build, daml codegen js.
• cd ui
• npm add --only=dev puppeteer wait-on @types/jest @types/node @types/puppeteer @types/wait-on per the Testing page.
• Run npm install.
• Get a this-branch version of the Testing docs page and copy the index.test.ts file from there.
• Run daml studio to create the file. Rename the dependency from create-daml-app to myproject in ui/src/index.test.ts, ui/src/component/MessageEdit.tsx and ui/src/component/MessageList.tsx. Verify that there are no errors after that.
• Run npm test. Marvel at the newfound green-ness.