Prepared OpenVINO 2024.6.0 migration

[artanokhov]

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

[artanokhov]

I didn't found so far any automatically created PR for migration to 2024.6.0 release.
Please point how we can detect it in the future, maybe we should fix this automatic or provide additional changes in openvino CF repo for enabling it?

[hmaarrfk]

Sometimes logs are here. https://conda-forge.org/status/#version but I don't see anything for openvino.

I feel like somebody recently started to add more warnings about the linter not being able to update things.

However, I suspect it is because the windows build failed?

Sometimes this bot takes like 1-2 days to pull in the update.

Once the windows build passes, please ping me again.