[Snyk] Security upgrade node from 18.19.1-alpine3.18 to 18.20.0-alpine3.18

[KaterynaBasik]

This PR was automatically created by Snyk using the credentials of a real user.

Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image. #### Changes included in this PR - Dockerfile We recommend upgrading to `node:18.20.0-alpine3.18`, as this image has only 0 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected. Some of the most important vulnerabilities in your base image include: | Severity | Priority Score / 1000 | Issue | Exploit Maturity | | :------: | :-------------------- | :---- | :--------------- | |  | **149** | Allocation of Resources Without Limits or Throttling
[SNYK-UPSTREAM-NODE-6564548](https://snyk.io/vuln/SNYK-UPSTREAM-NODE-6564548) | No Known Exploit | |  | **59** | HTTP Request Smuggling
[SNYK-UPSTREAM-NODE-6564550](https://snyk.io/vuln/SNYK-UPSTREAM-NODE-6564550) | No Known Exploit | --- **Note:** _You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs._ For more information: 🧐 [View latest project report](https://app.snyk.io/org/dsd-mobile/project/b2e8eed6-c04a-4ff8-af50-a79b02294195?utm_source=github&utm_medium=referral&page=fix-pr) 🛠 [Adjust project settings](https://app.snyk.io/org/dsd-mobile/project/b2e8eed6-c04a-4ff8-af50-a79b02294195?utm_source=github&utm_medium=referral&page=fix-pr/settings) [//]: # 'snyk:metadata:{"prId":"a07e1b43-b30c-4a44-80ed-a41108740b64","prPublicId":"a07e1b43-b30c-4a44-80ed-a41108740b64","dependencies":[{"name":"node","from":"18.19.1-alpine3.18","to":"18.20.0-alpine3.18"}],"packageManager":"dockerfile","projectPublicId":"b2e8eed6-c04a-4ff8-af50-a79b02294195","projectUrl":"https://app.snyk.io/org/dsd-mobile/project/b2e8eed6-c04a-4ff8-af50-a79b02294195?utm_source=github&utm_medium=referral&page=fix-pr","type":"auto","patch":[],"vulns":["SNYK-UPSTREAM-NODE-6564548","SNYK-UPSTREAM-NODE-6564550"],"upgrade":["SNYK-UPSTREAM-NODE-6564548","SNYK-UPSTREAM-NODE-6564550"],"isBreakingChange":false,"env":"prod","prType":"fix","templateVariants":["updated-fix-title","priorityScore"],"priorityScoreList":[149,59],"remediationStrategy":"vuln"}' --- **Learn how to fix vulnerabilities with free interactive lessons:** 🦉 [Allocation of Resources Without Limits or Throttling](https://learn.snyk.io/lesson/no-rate-limiting/?loc=fix-pr)

[github-actions[bot]]

Pull request title linting :rotating_light:

In order to merge this pull request, the title of the pull request should be prefixed by one of the available types.

Available types:

• feat: A new feature
• fix: A bug fix
• docs: Documentation only changes
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
• refactor: A code change that neither fixes a bug nor adds a feature
• perf: A code change that improves performance
• test: Adding missing tests or correcting existing tests
• build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
• ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
• chore: Other changes that don't modify src or test files
• revert: Reverts a previous commit

---

Examples

``` feat(grpc): add new endpoint refactor: combine class A and class B ci: update pull request linter style: change format of strings ```

:tipping_hand_person: For more examples, visit https://www.conventionalcommits.org/en/v1.0.0/#examples.

[dansvend]

Duplicate of #710