update safety check ignore list (data-dot-all#1310)

### Feature or Bugfix
- Bugfix

### Detail
* ignoring [70612](https://data.safetycli.com/v/70612/97c/) because
there is no resolution yet
* ignoring [70624](https://data.safetycli.com/v/70624/97c/) because
there is no resolution yet
* removing
[67599](https://data.safetycli.com/vulnerabilities/CVE-2018-20225/67599/)
because it's fixed

### Security
Please answer the questions below briefly where applicable, or write
`N/A`. Based on
[OWASP 10](https://owasp.org/Top10/en/).

- Does this PR introduce or modify any input fields or queries - this
includes
fetching data from storage outside the application (e.g. a database, an
S3 bucket)?
  - Is the input sanitized?
- What precautions are you taking before deserializing the data you
consume?
  - Is injection prevented by parametrizing queries?
  - Have you ensured no `eval` or similar functions are used?
- Does this PR introduce any functionality or component that requires
authorization?
- How have you ensured it respects the existing AuthN/AuthZ mechanisms?
  - Are you logging failed auth attempts?
- Are you using or adding any cryptographic features?
  - Do you use a standard proven implementations?
  - Are the used keys controlled by the customer? Where are they stored?
- Are you introducing any new policies/roles/users?
  - Have you used the least-privilege principle? How?


By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 license.

Makefile

@@ -49,7 +49,7 @@ check-security: upgrade-pip install-backend install-cdkproxy
 	pip install bandit
 	pip install safety
 	bandit -lll -r backend
-	safety check --ignore=51668,67599
+	safety check --ignore=51668,70612,70624
 
 test:
 	export PYTHONPATH=./backend:/./tests && \