refactor(db): Implement query_paged_as! macro to construct paginated queries that are still statically checked

[boxbeam]

Things to note:

• Every column is selected as non-nullable, which might not be desirable
• & must be used to separate the last column instead of , due to a number of limitations

This might be better drafted as a procedural macro? Let me know if you'd be open to that, it would be more code but wouldn't come with these compromises

[codecov]

Codecov Report

Attention: Patch coverage is 95.08197% with 6 lines in your changes are missing coverage. Please review.

Project coverage is 53.90%. Comparing base (d8628f1) to head (f77a6f9).
Report is 16 commits behind head on main.

Files	Patch %	Lines
ee/tabby-db-macros/src/lib.rs	92.40%	6 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1600      +/-   ##
==========================================
+ Coverage   52.03%   53.90%   +1.86%     
==========================================
  Files         113      115       +2     
  Lines        9263     9580     +317     
==========================================
+ Hits         4820     5164     +344     
+ Misses       4443     4416      -27     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[wsxiaoys]

this makes tabby-macros library only meaningful for tabby-db, correct? Maybe move it to ee/tabby-db-macros

[boxbeam]

I will do that, but I want to note that this has no actual dependency on tabby-db and has no feature flags associated with it, since it never actually uses that code, only generates syntax which refers to it. I was figuring that it would make sense to group all our macros in one place, if we want to add more.

[wsxiaoys]

consider move code that will be used by macros into a separate file, e.g src/macro_deps.rs

[boxbeam]

It's not only used by macros for the time being, so I think we should leave it here until the refactoring is complete.