Audit MCPServer constructor parameters

[maxisbey]

From the V2 checklist in #1253:

We need to recheck the constructor parameters of the MCPServer class. I did remove and refactor a bit, but we need to audit it a bit better.

PR #1732 renamed FastMCP to MCPServer and moved transport-specific options (host, port, stateless_http, etc.) to run(). However, the constructor still has parameters that may need further review:

• Are all remaining constructor parameters appropriate for the constructor vs. run()?
• Are there parameters that should be removed, renamed, or have their defaults reconsidered?
• Is the constructor signature clean and minimal for the common case?

This is a follow-up audit to ensure the MCPServer API surface is well-designed before V2 stabilizes.

Ref: Kludex's V2 checklist in #1253, follow-up to #1732

[Kludex]

I think the warm_on* parameters are unnecessary. I think we should raise on duplicated tool/resource/prompt name.

I'm also confused as to why we have 3 auth related parameters. @pcarleton Do you know why of this choice?