fix: increase duckdb memory limit to 80GB

[Taepper]

resolves the issue raised in slack of failing GISAID preprocessing on the staging server

Summary

duckdb memory_limit was set too conservative. This was done as previous duckdb versions did not conform to the memory limit for all features. This can now be raised to some higher limit.

PR Checklist

- [ ] All necessary documentation has been adapted or there is an issue to do so.
- [ ] The implemented feature is covered by an appropriate test.

[github-actions]

This is a preview of the changelog of the next release:

0.2.18 (2024-09-12)

Features

• do not abort on assertment failures (4e5f598)
• panic: add ASSERT, UNREACHABLE, UNIMPLEMENTED, safer env var (867d08f)
• update duckdb version (577c1b2)

Bug Fixes

• duplicate key in sample.ndjson (c9b5232)
• increase duckdb memory limit to 80GB (ae4532d)
• order of randomized tests changed (d29b2f2)