Add mmdeploy export

[eunwoosh]

Summary

This PR enables mmdeploy export to OTX2.0. Currently, detection and instance segmentation need mmdeploy for export.
This PR includes

• modify Exporter design for mmdeploy
• Add MMdeployExporter
• Add mmdeploy config for models
• Fix OVInstanceSegmentationModel

TBD

• This PR doesn't support exporting tiling.

Difference between mmdeploy export in OTX 1.X and OTX 2.0

When exporting a model w/ mmdeploy in OTX, model is converted to ONNX and ONNX is converted to OV.
In OTX 1.X, mmdeploy is used for both conversion but OTX 2.0 uses OpenVINO to convert ONNX model to OV.
It's for not falling behind latest update in OV because current latest mmdeploy is still using OpenVINO 22.03 but current latest version is 23.02.
I also removed unused code as mmdeploy ONNX -> OV is dropped.

Update integration test.

Export model score can be unstable if a model isn't fully trained.
To prevent it, some detection models get more epoch.
maskrcnn_swint isn't trained at all, so skip it in the test.

python format mmdeploy config

Because config files given by mmdeploy has python format as default,
I leave it as it is not to give user additional burden to get mmdeploy configs for new models in OTX.

P.S. I bring some code unused now but for future (e.g. export tilling, configurable parameter related setting)

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

[sungmanc]

It seems that there are many TODO or workaround in this PR. Could we make the separate backlog for those issues to avoid the missing ?

[yunchu]

For you guys information, currently there is an issue using the mmdeploy to the v1. that's related with the protobuf package that is used by mmdeploy and the protobuf v3 has some vulnerability issue so that required to be updated to the v4 but the latest version of mmdeploy used v3 yet.