Cardano Updates

feat: enrich /governance/dreps with voting power, status, metadata + filter/sort params

Drops the boolToSqlParam helper and the LOWER(\$N::text) = 'true'/'false'
SQL gymnastics. ajv already coerces query strings to booleans from the
type:boolean schema, and node-postgres serializes booleans into the wire
format Postgres expects — so the parameters can flow through end-to-end
without a string detour. The boolean SQL is also shorter:

  (NOT c.registered) = \$5::boolean   -- retired filter
  expired_predicate = \$6::boolean    -- expired filter

The ::boolean annotation is still needed for the same parameter-type
inference reason as before.

Route handler now selects the SQL key and its parameter array together
(single { key, params } literal per branch) so the two can't drift
independently when one is edited.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

node-postgres sends JS null without a type tag, so Postgres has to infer
each parameter's type from how it's used in the SQL. When a nullable text
param (order_by, retired, expired) appears only in IS NULL checks and OR
clauses, inference can give up and raise 42P08 "could not determine data
type of parameter $N" — observed on /governance/dreps?retired=true.

Pinning the parameter slot's type with $N::text bypasses inference. The
::text is on the parameter, not the value — works equally for NULL and
'true'/'false'.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

voting_anchor.data_hash is NOT NULL in db-sync, so metadata_hash is
guaranteed non-null whenever metadata_url is non-null (both come from
the same row). TS can narrow metadata_url from the explicit null check
but doesn't know about the inter-column correlation; asserting the type
here keeps the openapi schema's required-string contract.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

Mirrors the 404 behavior of /dreps/:drep_id/metadata in list form. When a
DRep has never carried a voting anchor (e.g. special DReps such as
drep_always_abstain), the metadata field is now `null` instead of an
object with all-null inner fields.

Bumps @blockfrost/openapi to 0.1.89-beta.1 for the matching schema change.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

The single-DRep /dreps/{id} query defines expired as
  (current_epoch - last_active_epoch) > drep_activity
which is satisfied iff last_active_epoch <= current_epoch - drep_activity - 1.

The filtered SQL was computing the threshold epoch as
  current_epoch - drep_activity
which marks a DRep as expired when its last activity was exactly drep_activity
epochs ago — contradicting the strict-greater-than semantics. Subtract 1 to
align with the single-DRep query.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

If the boundary epoch has no blocks, MAX(tx.id) returns NULL and the
`expired` predicate evaluates to NULL instead of FALSE, which silently
drops every row from BOTH `expired=true` and `expired=false` filter
results. COALESCE to 0 so the predicate is always a real boolean and
the "fails open" comment in the file is actually true.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

Embeds the per-DRep fields previously requiring N+1 calls to /dreps/{id} and
/dreps/{id}/metadata into the paginated /dreps response: amount, has_script,
retired, expired, last_active_epoch, and the off-chain metadata object.

Adds query params:
- order_by=amount  (in addition to existing order=asc|desc)
- retired=true|false
- expired=true|false

Routes to a separate SQL path when retired/expired filters are present, since
filtering on computed fields requires full-table aggregation; the unfiltered
path keeps its page-first plan and stays fast.

Depends on a future @blockfrost/openapi release exposing the new schema and
query params.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>