Middleware auth, traces page efficiency

[dinmukhamedm]

• Add project auth to middleware (for now edge calls node to check)
• Don't join spans on the count spans query
• Another slight optimization on spans query
• Initial link between spans and datapoints
• various UX improvements

---

Important

This pull request enhances middleware authentication, optimizes database schema and queries, and improves frontend UX and performance.

• Middleware:
  • Added project-based authentication in middleware.ts using a POST request to /api/auth.
  • Redirects unauthorized users to /not-found.
• Database:
  • Created datapoint_to_span table with foreign keys to dataset_datapoints and spans.
  • Added indexes to spans and traces tables for performance optimization.
  • Updated labels table to set value column as NOT NULL.
• Frontend:
  • Removed isCurrentUserMemberOfProject checks from multiple API routes.
  • Added SpanDatasets component to display datasets linked to a span.
  • Enhanced DataTable component with row selection and pagination features.
  • Improved SessionsTable and TracesTable with better filtering and pagination.
  • Various UI enhancements in Dataset, ExportSpansDialog, and TraceView.

^{This description was created by for e4dccaf. It will automatically update as commits are pushed.}

[ellipsis-dev]

❌ Changes requested. Reviewed everything up to e4dccaf in 1 minute and 34 seconds

More details

• Looked at 4251 lines of code in 37 files
• Skipped 1 files when reviewing.
• Skipped posting 2 drafted comments based on config settings.

1. frontend/lib/db/migrations/schema.ts:525

• Draft comment:
  Ensure that the primary key definition here matches the SQL migration file to maintain consistency between the schema and the database.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The datapointToSpan table in the schema file has a primary key defined on three columns: datapointId, spanId, and projectId. This matches the SQL migration file, ensuring consistency between the schema and the database.

2. frontend/lib/db/migrations/0004_worthless_kitty_pryde.sql:6

• Draft comment:
  Ensure that the primary key definition here matches the schema file to maintain consistency between the schema and the database.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The datapointToSpan table in the SQL migration file has a primary key defined on three columns: datapoint_id, span_id, and project_id. This matches the schema file, ensuring consistency between the schema and the database.

Workflow ID: wflow_2TFF4k6LQq9SPwt3

---

Want Ellipsis to fix these issues? Tag @ellipsis-dev in a comment. You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[ellipsis-dev]

Forwarding all request headers can lead to security vulnerabilities. Consider explicitly setting only the necessary headers for the internal request.

Suggested change

	...Object.fromEntries(req.headers),
	'Content-Type': 'application/json',