Add support for parsing AUTO, HETERO and MULTI from json config

[preetha-intel]

Description

Add parsing for different mode execution via config file in OVEP

Motivation and Context

Support for the AUTO properties like ENABLE_RUNTIME_FALLBACK needs to be added in OVEP.

Sample .json file for this feature is :

auto_config.json

{
"AUTO":
{"ENABLE_STARTUP_FALLBACK":"NO",
"ENABLE_RUNTIME_FALLBACK" : "NO",
"EXECUTION_MODE_HINT" : "ACCURACY"}
}

The properties for a specified hardware is obtained from OV. Adding the syntax to print supported OV properties for a device using C++ API

auto device = "AUTO";
auto device_properties = ov::core.get_property(device, ov::supported_properties);
  //print device properties
  std::cout << " Properties for " << device << " : " << std::endl;
  for(auto& it : device_properties) {
    std::cout << it << std::endl;
  }

For checking whether the property is set correctly during OV model compilation, we can get and print the properties from OV compiled model using the below snippet in C++

    // output of the actual settings that the device selected
    auto compiledModel = ov::core.compile_model(onnx_model, ov::Tensor(), hw_target, device_config);
    auto supported_properties = compiledModel.get_property(ov::supported_properties);
    std::cout << "Model:" << std::endl;
    for (const auto& cfg : supported_properties) {
        if (cfg == ov::supported_properties)
            continue;
        auto prop = compiledModel.get_property(cfg);
        if (cfg == ov::device::properties) {
            auto devices_properties = prop.as<ov::AnyMap>();
            for (auto& item : devices_properties) {
                std::cout << "  " << item.first << ": " << std::endl;
                for (auto& item2 : item.second.as<ov::AnyMap>()) {
                    std::cout << "    " << item2.first << ": " << item2.second.as<std::string>() << std::endl;
                }
            }
        } else {
            std::cout << "  " << cfg << ": " << prop.as<std::string>() << std::endl;
        }
    }

HAFP-3004

[sfatimar]

Please list what unit testing you have done for this code fix

[sfatimar]

Please resolve comments and close on this PR.

[MayureshV1]

@vthaniel , @jatinwadhwa921 - Can we create a test case for load_config feature and if it exists add AUTO, HETERO, MULTI into the tests.

@preetha-intel . Do we have a methodology to query whether a feature is set correctly in OpenVINO.
For e.g.: If "ENABLE_STARTUP_FALLBACK":"NO", can we query OV to check whether it was disabled?

[preetha-intel]

@vthaniel , @jatinwadhwa921 - Can we create a test case for load_config feature and if it exists add AUTO, HETERO, MULTI into the tests.

@preetha-intel . Do we have a methodology to query whether a feature is set correctly in OpenVINO. For e.g.: If "ENABLE_STARTUP_FALLBACK":"NO", can we query OV to check whether it was disabled?

There is OPENVIINO_LOG_LEVEL=5 env variable that prints the properties of OV compiled model. But its working only for AUTO and MULTI. Looks like HETERO is broken

[TejalKhade28]

@vthaniel , @jatinwadhwa921 - Can we create a test case for load_config feature and if it exists add AUTO, HETERO, MULTI into the tests.

@preetha-intel . Do we have a methodology to query whether a feature is set correctly in OpenVINO. For e.g.: If "ENABLE_STARTUP_FALLBACK":"NO", can we query OV to check whether it was disabled?

We can test load_config feature for AUTO, MULTI with the OPENVINO_LOG_LEVEL=5 env variable, but this does not work for HETERO. The logs for HETERO are not shown up.

[preetha-intel]

@TejalKhade28 We can use the LOG_LEVEL config option to get the compiler level debug logs.
Update the json file with

auto_config.json

{
"AUTO":
{"ENABLE_STARTUP_FALLBACK":"NO",
"ENABLE_RUNTIME_FALLBACK" : "NO",
"EXECUTION_MODE_HINT" : "ACCURACY",
"LOG_LEVEL" : "LOG_DEBUG"}
}

[sfatimar]

@preetha-intel can you please rebase this branch

[preetha-intel]

@sfatimar Rebased and validated