fix: allow pydantic 2.13+, run pytest in PR validation, drop committed output.zip

[LukasParke]

Summary

• Allow Pydantic 2.13 so the SDK can be used with Home Assistant #764: removes the pydantic <2.13 cap, which blocks Home Assistant and other apps on current pydantic. The new constraint is >=2.11.2,<3. I set it in .speakeasy/gen.yaml additionalDependencies.main so the change survives regeneration, and mirrored it in pyproject.toml. The SDK imports and the test suite pass on pydantic 2.13.5.
• Test suite is red on main and CI never runs it: pytest is in neither the dev group nor pr-validation.yaml #585: pytest was never installed or run, so CI did not catch that tests/test_responses_namespace.py was already failing on main. Two assertions there had gone stale: beta.responses is now a separate BetaResponses class, and analytics moved from beta to the top-level client. This PR:
  • adds pytest and pytest-asyncio to the dev group through gen.yaml/pyproject.toml (uv.lock is updated),
  • adds a Tests (pytest) step to pr-validation.yaml,
  • changes the test to compare the public method sets of responses and beta.responses and to check client.analytics.
• Repo hygiene: drop empty output.zip, fix dead .speakeasy gitignore rules, resolve dangling Anthropic Messages tag #592 (part): removes the committed output.zip and adds it to .gitignore.

Result: uv run --group dev pytest reports 4 passed, with both the locked pydantic and 2.13.5.

Searched existing PRs; none matched.

Link to Devin session: https://openrouter.devinenterprise.com/sessions/78072f08dc274fda9d8309045b1ab806
Open in Devin Desktop: https://openrouter.devinenterprise.com/desktop/session/78072f08dc274fda9d8309045b1ab806?variant=devin
Requested by: @LukasParke

[devin-ai-integration]

I'll fix CI failures and address comments from users with write access that start with 'Devin'.

• Disable automatic comment, CI, and merge conflict monitoring

---

Original prompt from Luke

SYSTEM:
<latest_message>
Luke Parke (U0BF2BKT52N) [ts=1791235775.813579]: @Devin audit all open issues on our public Typescript, Python, and Go SDKs, and the terraform Provider repo, and list out the unique problems, and vet them to determine validity and severity
</latest_message>

=== BEGIN THREAD HISTORY (in #agents) ===
Luke Parke (U0BF2BKT52N) [ts=1791235775.813579]: @Devin audit all open issues on our public Typescript, Python, and Go SDKs, and the terraform Provider repo, and list out the unique problems, and vet them to determine validity and severity
=== END THREAD HISTORY ===
Channel ID: C07UF9XLTFF
Thread URL: https://openrouter.slack.com/archives/C07UF9XLTFF/p1791235775813579?thread_ts=1791235775.813579&amp;cid=C07UF9XLTFF

The <latest_message> is the message that you should use to guide your goals + task for this session, and you should use the rest of the slack thread as context.
A [ts=...] marker on a Slack message is that message's timestamp. To act on a specific message with the slack tool (e.g. adding an emoji reaction via the reaction command), pass that value as timestamp along with the Channel ID — no extra lookup call is needed.