Add configuration to segmentation IR

[sovrasov]

Summary

This PR adds ModelAPI-specific meta information into segmentation model IR.

How to test

Checklist

• I have added unit tests to cover my changes.​
• I have added integration tests to cover my changes.​
• I have added e2e tests for validation.
• I have added the description of my changes into CHANGELOG in my target branch (e.g., CHANGELOG in develop).​
• I have updated the documentation in my target branch accordingly (e.g., documentation in develop).
• I have linked related issues.

License

• I submit my code changes under the same Apache License that covers the project.
  Feel free to contact the maintainers if that's a concern.
• I have updated the license header for each file (see an example below).

# Copyright (C) 2023 Intel Corporation
# SPDX-License-Identifier: Apache-2.0

[goodsong81]

Embedding itself here looks OK to me.
Would you somehow check whether the IR models from old OTX (Geti) without this segmentation metadata will be still working well without issues? I mean backward compatibility.

[sovrasov]

Embedding itself here looks OK to me. Would you somehow check whether the IR models from old OTX (Geti) without this segmentation metadata will be still working well without issues? I mean backward compatibility.

This information is not used by OTX, so such issues can not arise (like we don't observe it in case of classification and detection).

[goodsong81]

Embedding itself here looks OK to me. Would you somehow check whether the IR models from old OTX (Geti) without this segmentation metadata will be still working well without issues? I mean backward compatibility.

This information is not used by OTX, so such issues can not arise (like we don't observe it in case of classification and detection).

Yes, I agree. When the new ModelAPIs will replace current OMZ ModelAPIs, we need to check such compatibility anyway. Thank you for clarification. :)

[sovrasov]

Embedding itself here looks OK to me. Would you somehow check whether the IR models from old OTX (Geti) without this segmentation metadata will be still working well without issues? I mean backward compatibility.

This information is not used by OTX, so such issues can not arise (like we don't observe it in case of classification and detection).

Yes, I agree. When the new ModelAPIs will replace current OMZ ModelAPIs, we need to check such compatibility anyway. Thank you for clarification. :)

yeah, integration of ModelAPI and it's consequences for geti versions compatibility is a standalone discussion. It's complicated, since MAPI doesn't know about config.json, so we may need patch IRs in a JIT manner.