Disable input count validation flag

[przepeck]

🛠 Summary

CVS-187884
Adding flag --disable_input_count_validation to match TFS behavior with number of sent input entries grater then model input count

🧪 Checklist

• Unit tests added.
• The documentation updated.
• Change follows security best practices.
  ``

[Copilot]

Pull request overview

This PR introduces a new server flag --disable_input_count_validation intended to relax inference-request validation behavior (to align with TFS behavior around extra request inputs), and wires it through CLI parsing, runtime validation, tests, and documentation.

Changes:

• Added CLI/config plumbing for disable_input_count_validation and exposed it via ovms::Config.
• Modified request validation to conditionally skip input-count validation when the flag is enabled.
• Added/updated unit tests and documentation to cover the new flag.

Reviewed changes

Copilot reviewed 10 out of 10 changed files in this pull request and generated 6 comments.

Show a summary per file

File	Description
src/test/predict_validation_test.cpp	Adds KFS validation tests for the new flag using a config-toggling test fixture.
src/test/ovmsconfig_test.cpp	Extends CLI parsing tests to include the new flag and verifies its default value.
src/predict_request_validation_utils.hpp	Gates validateNumberOfTensors() behind the new config flag.
src/config.hpp	Declares Config::disableInputCountValidation().
src/config.cpp	Implements Config::disableInputCountValidation().
src/cli_parser.cpp	Adds the --disable_input_count_validation CLI option and maps it into ServerSettingsImpl.
src/capi_frontend/server_settings.hpp	Adds disableInputCountValidation to server settings with a default of false.
src/BUILD	Adds deps to a CAPI library target (currently used to satisfy new header inclusion requirements).
docs/security_considerations.md	Documents security implications of enabling the new flag.
docs/parameters.md	Documents the new CLI parameter and its behavior.

Suppressed comments (1)

src/test/predict_validation_test.cpp:144

• TearDown() ignores the return value of Config::parse(...) when restoring global settings. If this fails, it can pollute subsequent tests in the same binary.

        ovms::Config::instance().parse(&originalServerSettings, &originalModelsSettings);

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[przepeck]

I cannot agree with this comment, error "INVALID_MISSING_INPUT" is better for described scenario