Pin OpenVINO runtime commit to avoid circular dependency issues

[CuriousPanCake]

Pin OpenVINO runtime commit to avoid circular dependency issues

• Tickets:
  CVS-165769

Signed-off-by: Andrii Staikov andrii.staikov@intel.com

[CuriousPanCake]

Required for merging openvinotoolkit/openvino#32570
Otherwise, the GenAI code is going to be broken

[Wovchena]

What particular OV change is going to break GenAI? I though OV is going to extend its API, not shrink.

There's also probably backward incompatibility introduced by OV. Suppose someone has their own implementation which happens to match current OV GenAI exactly.

[CuriousPanCake]

You're right, we'll have more code in runtime, less in GenAI, but

1. Merging the runtime PR is not possible without pining the GenAI version. Otherwise, once it is merged, the GenAI code is not going to work correct: you're going to always have exceptions at the PA initialization stage hence falling back to the SDPA implementation.

2. Similarly, it's not possible to merge the GenAI changes first as runtime is not supporting them yet: the CI is going to be red and the GenAI pipelines are not going to work properly.

That's why we thought it's going to be good to

1. Pin the runtime version
2. Merge OV runtime changes
3. Merge GenAI changes

Please, let me know if you need more information

[Wovchena]

(2) is clear. My questions are about (1) (still not answered)

[mryzhov]

(2) is clear. My questions are about (1) (still not answered)
When we merge the new transformation in OV then models will be converted (sdpa->pa) by moc transformation and in genai pipeline the old transformation will fail on this model.

[CuriousPanCake]

Talked with Vladimir offline, he approves the changes