docs: add Drizzle ORM to third-party tools

[PedroHenrique0713]

Closes #70.

This picks up where #71 stopped. That PR had @nwoolmer's go-ahead and only needed the example aligned to the trades table; the author made the change, asked for another review in October 2024, and the PR went stale and was closed six months later without landing. Credit for the original idea and first draft goes to @Mrinank-Bhowmick. This is a fresh page rather than a revival of that branch, since the docs tree moved in the meantime.

Everything here was run, not assumed

Verified against QuestDB 10.0.1 with drizzle-orm 0.45.2 and postgres 3.4.9, driving each case through the query builder:

operation	result
insert	works
select with where / orderBy / limit	works
groupBy with aggregation	works
SAMPLE BY via db.execute(sql`` ``)`	works
update	works
delete	fails

So the page documents what the combination actually does:

• DELETE is called out as unsupported, with a pointer to dropping a partition instead. QuestDB has no row-level delete, and db.delete(...) fails against it.
• Migrations are out, because the table needs a designated timestamp and a partitioning strategy that drizzle-kit does not express. The page shows SQL DDL for the table and a matching Drizzle schema for querying it.
• QuestDB SQL extensions get their own section: SAMPLE BY, LATEST ON and ASOF JOIN have no builder equivalent and go through db.execute().
• The page points ingestion-heavy use at the Node.js client rather than the ORM, since that is what ILP is for.

One thing I deliberately left out: I first tested with prepare: false on the postgres client, then re-ran without it. It works either way, so the page does not mention it rather than carrying a setting nobody needs.

Uses the trades table throughout, which is the alignment @nwoolmer asked for on the original PR.

Registered in integrations/overview.md under Other Tools and in sidebars.js next to SQLAlchemy. All seven internal links in the page resolve to existing files.