[DOP-28871] Add artificial filters by Operation/Run id

[dolfinus]

Change Summary

Run and Operation models have primary key (id, created_at). When we have only filters like created_at >= :since, this leads to scanning all primary keys, because B-tree indexes are prefix-based.

As ids are UUIDv7, and created_at is always UUID internal timestamp, we can generate artificial filters like created_at >= since AND id >= :min_id, to limit range of ids to be scanned, improving query plan. Same for created_at <= :until and id >= :max_id.

This affects only some REST API endpoints, as consumer already access entries by specific id, not the date range.

Also, tables like Input, Output, ColumnLineage has primary key (created_at, id), and the only filter used here is created_at >= :since, so these remain unchanged.

Related issue number

Checklist

• Commit message and PR title is comprehensive
• Keep the change as small as possible
• Unit and integration tests for the changes exist
• Tests pass on CI and coverage does not decrease
• Documentation reflects the changes where applicable
• docs/changelog/next_release/<pull request or issue id>.<change type>.rst file added describing change
  (see CONTRIBUTING.rst for details.)
• My PR is ready to review.

[github-actions]

Coverage Report •

File	Stmts	Miss	Cover	Missing
data_rentgen/db/repositories
operation.py	61	11	81%	132–133, 159–160, 163–164, 166–167, 169, 171, 179
run.py	90	29	67%	187–188, 190–191, 193, 195, 203, 206–207, 209–210, 217–218, 221–224, 227–228, 231, 246–248, 256, 273–275, 277–278
data_rentgen/utils
uuid.py	54	9	83%	111–112, 117–123
TOTAL	6962	397	94%