Fix: Prevent dangling reference crash by correcting C++ return value policy.

[sungeunk]

This PR fixes a critical memory safety issue where a C++ function was returning a const & reference to Python without proper lifetime management.

The Problem: The returned reference's lifetime was tied to a parent C++ object. When the parent object was garbage-collected in Python, the reference became a dangling pointer, leading to unpredictable segmentation faults (use-after-free).

The Solution: This has been resolved by applying the py::return_value_policy::reference_internal policy to the binding. This ensures the parent object's lifetime is extended as long as the returned reference is in use by Python, preventing any memory corruption.

Tickets:

• 174729

[Copilot]

Pull Request Overview

This PR addresses a lifecycle management issue in the Python bindings for OpenVINO's CompiledModel class by adding py::return_value_policy::reference_internal to three overloaded output() method bindings. This ensures that returned output objects maintain a proper reference to their parent CompiledModel instance, preventing premature deallocation and potential use-after-free scenarios.

Key Changes:

• Added py::return_value_policy::reference_internal to all three output() method overloads (no-arg, by-index, and by-name variants)

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[sungeunk]

@mlukasze Could you please merge this PR when you have a moment?