feat(apidocs): Lint undeclared serializers on public endpoints

[azulus]

Adds S025, which reports a public endpoint that validates its input with one serializer while naming a different one in @extend_schema.

The schema is generated from what an endpoint declares, while the runtime accepts whatever validates, so when those disagree the endpoint accepts a shape no generated client can send. Twelve endpoints disagree today, six on the query string and six on the request body. project_repo.py is representative: it declares an inline_serializer carrying only repositoryId, then validates the body with ProjectRepoSerializer.

This is the first of three rules covering endpoint input, so it also adds ENFORCED, which names the rules whose diagnostics are fatal. It ships empty and nothing here can fail a build. That mirrors how the Response[T] linter rolled out — land the rule dark, drain the backlog, then gate — and SENTRY_INPUT_LINT_ALL=1 emits every rule regardless so a plain flake8 run over the tree produces the inventory to drain.

S025 only fires when the callee looks like a class. That skips plain calls which happen to take a data= argument, and classes chosen at runtime such as serializer_cls(data=...); the schema could not name either of those, so reporting them would be noise rather than backlog.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 94f77b8. Configure here.}

[sentry]

Sentry Snapshot Testing

Name	Added	Removed	Changed	Renamed	Unchanged	Skipped	Status
sentry-frontend sentry-frontend	-	-	-	-	-	-	✅ 481 uploaded

No base snapshot found for 284f8f38eaa7bdd0c675181556bfbbf2a9acdefb. Make sure snapshots are uploaded from your main branch.

⚙️ sentry-frontend Snapshot Settings