Fix: Defer axis validation in reduce operations to compile/runtime

[sshekhar563]

Summary

This PR addresses issue #33261 by deferring axis validation for reduce operations from node creation time to compile/runtime, improving the user experience when building models with the Python opset API.

Problem

Previously, when creating reduce operations (ReduceMean, ReduceMax, ReduceMin, etc.) with out-of-range axes via the Python opset API, validation would fail immediately during node construction with a RuntimeError. This was surprising behavior since users typically expect validation to occur at core.compile_model() time, not during model building.

Before (problematic behavior):

import openvino.opset1 as ops
x = ops.parameter([2], name="x")  # 1D tensor
y = ops.reduce_mean(x, axes=[1])  # axis 1 is out of range for rank 1
# RuntimeError: Axis 1 out of the tensor rank range [-1, 0]

**After (improved behavior):**

import openvino.opset1 as ops
x = ops.parameter([2], name="x")  # 1D tensor  
y = ops.reduce_mean(x, axes=[1])  # Node created successfully with dynamic output shape
model = core.compile_model(model, "CPU")  # Validation happens here with clear error message


Fixes #33261

[praasz]

This is not correct.
In OpenVINO if output shape cannot be calculated correctly because of invalid inputs the exception must be thrown.

[sshekhar563]

"Understood. I attempted to defer the validation to improve the user experience as requested in the issue, but I see now that core shape inference requires strict validation when inputs are known. I will revert this change.
I will instead update the PR to add a documentation warning (docstring) and a unit test to formalize this 'fail-fast' behavior, which addresses the original issue's request for better clarity."

[sshekhar563]

@praasz I have reverted the changes to reduce_shape_inference.hpp. Instead, I am converting this PR to a Documentation & Test fix:
Add a unit test (reduce_invalid_axis_out_of_range) to strictly enforce that this validation throws the correct exception.
Updated the Python docstrings to warn users that invalid static axes will raise a RuntimeError at node creation time.

[praasz]

@praasz I have reverted the changes to reduce_shape_inference.hpp. Instead, I am converting this PR to a Documentation & Test fix: Add a unit test (reduce_invalid_axis_out_of_range) to strictly enforce that this validation throws the correct exception. Updated the Python docstrings to warn users that invalid static axes will raise a RuntimeError at node creation time.

The unit test can be added to show there is exception on invalid inputs.

Docstring update is not required as this is default action for OV nodes.
@p-wysocki could you look at it?