Fix async demo in exportable code

[GalyaZalesskaya]

Summary

This PR fixes the crush of demo in exportable code started in async mode. The issue was caused by the unsupported annotation format returned from async pipeline (Detection instance instead of np.array instance).

• Converted prediction results to np.array format
• Fixed names used for demo outputs if the original input names can't be used

Related issue: CVS-84793

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

[jaegukhyun]

Do we have any test method for demo codes?

[GalyaZalesskaya]

@jaegukhyun Yes, at least in e2e tests:

training_extensions/tests/e2e/cli/detection/test_detection.py

Line 216 in 63dcbd7

def test_otx_deploy_openvino(self, template, tmp_dir_path):

This test deploys the model, runs the exportable code demo, and saves the output. Then it validates that demo didn't crash and the output was saved.
Tests missed this use case because there is no test for async inference, the sync was used by default

[jaegukhyun]

@GalyaZalesskaya Thanks for reply, do you have any plan to add async test to e2e?

[GalyaZalesskaya]

@jaegukhyun Thank you for this suggestion. I'll add async exportable code demo tests in this PR