Use new sql interpolator in more DAOs, clean up

[fm3]

• propagates the use of the new sql interpolator with q"myQuery" that was introduced in Composable sql interpolation #6718 to more DAOs
• also adapts the types of the access queries (meaning the DAOs that are NOT yet adapted must re-stringify the access queries using .debugInfo
• splits classes of the file SQLHelpers into individual files
• adds support for enums, boundingboxes, vec3ints, arrays in sql interpolator

URL of deployed dev instance (used for testing):

• https://sqlrefactoring.webknossos.xyz

Issues

• contributes to Use composable SQL interpolation syntax for all queries #6721

TODO

• split SQLHelpers file, one file per class
• make access queries sqlTokens
• solve setting custom enumerations
• fix setting varchar[] (e.g. annotation tags)
• fix setting nulled jsonb
• fix setting Vec3Double
• check that error logging does not leak user data

Follow-up

• adapt all remaining queries
• remove then-unused escaping/unescaping code
• remove then-unused SqlTypeImplicits trait
• check that no usages of #$ remain
• check that no usages of debugInfo remain
• check that no usages of sql"" and sqlu"" remain, remove their import
• replace the Any/match approach to an implicit conversion approach to re-enable type checks at compile time

Steps to test:

• Test creating/importing/updating/deleting datasets, annotations, private links, folders
• Test with multi-user setup that access checks still work (e.g. dataset list, with folder permissions)
• CI helps as well
• do some monkey-testing of things that I am not thinking of 😅

---

• Ready for review

[fm3]

@normanrz Could you have a look at the changes in the SqlInterpolation file, and possibly check a few usages to see if I use this the way you intended it? @jstriebel agreed to look at the other changes :) It would also be appreciated if you could do some random testing. The fact that all SQL errors are logged and reported to slack makes me optimistic that we should find errors quickly

[normanrz]

Looks good in general. A few notes:

• For INSERTs, you could use SqlToken.tuple(...) to supply the values instead of interpolating them separately into the query
• Not sure whether boolean constants should be written in or passed in
• Please add tests for each new datatype that you added to SqlValue
• We should think of more helper functions to make inserts, updates and upserts less verbose
• Since you migrated all the big DAOs, it should be quick to do the rest, no?

[fm3]

Thanks for your feedback!

• I changed the boolean constants to pass values
• I added tests
• I hope to adapt the remaining DAOs in the coming days, but I think a separate PR for that would make sense. There are still more than 100 queries to be adapted.
• I created follow-up issue SQL helper functions for updates, inserts, upserts #6730 for the helper functions, as it is not immediately obvious to me how to design them

[jstriebel]

LGTM, all things that looked weird are already part of the follow-up points 👍 🚀
Props for adding tests! ❤️