feat: add full-text injection limits configuration and validation

[chenyme]

Summary

Support optional full-text injection limits for file context. Admins can now disable the full-text injection limit switch to keep full-text injection enabled without enforcing byte, token, or PDF page thresholds. Individual limits also support empty or 0 values as unlimited.

Change type

• Bug fix
• Feature
• Documentation
• Refactor
• Configuration / deployment
• Security hardening
• Other

Affected areas

• Frontend / UI
• Backend / API
• Authentication / authorization
• Conversations / streaming
• Files / RAG / extraction
• Model routing / providers
• MCP / tools
• Billing / payments
• Admin console
• Deployment / Docker / configuration
• Documentation

Verification

• cd backend && go test ./...
• cd frontend && pnpm lint
• git diff --check

Screenshots, API examples, or logs

N/A

Configuration, migration, and compatibility notes

Adds a new dynamic setting: file:full_context_limit_enabled, defaulting to true.

Backward compatibility is preserved: existing deployments keep the current full-text injection thresholds enabled by default. Disabling the switch only changes runtime behavior and does not erase the stored byte, token, or PDF page threshold values.

Documentation

• Documentation is not needed for this change.
• Documentation was updated.
• Documentation still needs to be updated.

Security and privacy

• No secrets, tokens, credentials, local config, or personal data are included.
• User data access remains scoped by authenticated user context unless an admin-only path explicitly requires broader access.
• Security-sensitive behavior was reviewed, including authentication, authorization, provider routing, file processing, billing, and admin APIs where relevant.

Checklist

• I searched existing issues and pull requests.
• Changes are focused and do not include unrelated refactors.
• Tests or static verification were run where practical.
• User-facing behavior, deployment steps, API contracts, or configuration changes are documented.
• Generated artifacts are included only when this project explicitly requires them.
• Caches, build output, .pyc files, .env files, and local storage data are not committed.