Deprecate deepseek-chat and deepseek-reasoner model aliases

[sumansahoo1]

Summary

Mark deepseek-chat and deepseek-reasoner as deprecated across all providers instead of deleting them.

Changes

• providers/anyapi/models/deepseek/deepseek-chat.toml: added status = "deprecated"
• providers/anyapi/models/deepseek/deepseek-r1.toml: added status = "deprecated"
• providers/openrouter/models/deepseek/deepseek-chat.toml: added status = "deprecated"
• providers/orcarouter/models/deepseek/deepseek-chat.toml: added status = "deprecated"
• providers/orcarouter/models/deepseek/deepseek-reasoner.toml: added status = "deprecated"

The underlying model metadata files (models/deepseek/deepseek-chat.toml and models/deepseek/deepseek-reasoner.toml) are preserved without changes (the ModelMetadata schema does not support status).

Why

DeepSeek has deprecated the deepseek-chat and deepseek-reasoner identifiers in favor of deepseek-v3.1 and deepseek-r1-0528. Following the repo convention of using status = "deprecated" instead of hard-deleting files.

[oskarkocol]

1. There are still live for 3 more weeks ( until 2026-07-24). What's the benefit of deleting them now?
2. The repo convention I see is sunsetting models with a flag: status = "deprecated" instead of hard delete. Would this work here?
3. This PR only touches providers/deepseek/*. The resellers still list them (e.g. on openrouter, orcarouter, anyapi etc). Is this intentional?

I'm curious what you think Aiden 👂

[rekram1-node]

This does not follow our patterns, will not be merging in current state.

[sumansahoo1]

@rekram1-node Thanks for the feedback. Updated the PR to use status = "deprecated" instead of deleting.

[oskarkocol]