[api] improve insert performance when persisting features data from CSV uploads [MRXN23-256]

[yulia-bel]

Csv feature upload performance improve (setting CTE as NOT MATERIALIZAED)

Overview

Adding logs and small performance improvement for bulk insert query - according to tests and logs analysis the fastest way for now is to set CTE used for features_data inserts as NOT MATERIALIZED and using chunks of 1000 values.

Some postgres analyse results:

Possible further solutions - inserting data with async jobs, refactoring geometries handling for features data uploaded via csv.

Designs

Link to the related design prototypes (if applicable)

Testing instructions

Please explain how to test the PR: ID of a dataset, steps to reach the feature, etc.

Feature relevant tickets

Link to the related task manager tickets

---

Checklist before submitting

• Meaningful commits and code rebased on develop.
• If this PR adds feature that should be tested for regressions when
  deploying to staging/production, please add brief testing instructions
  to the deploy checklist (docs/deployment-checklist.md)
• Update CHANGELOG file

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
marxan	✅ Ready (Inspect)	Visit Preview	Aug 1, 2023 3:37pm

[hotzevzl]

while we think about a more resilient (as in, given the many moving parts) solution, this does what it says on the tin.

not too happy about the way this does not scale (as discussed, it's likely because we'd need a different query setup altogether), but again, very much good enough for now.