Add model category attributes to model template

[goodsong81]

Summary

• Add model category fields to specify category, deprecation, default model

model_category: {SPEED|BALANCE|ACCURACY|OTHER}, default to OTHER
model_status: {ACTIVE|DEPRECATED}, defaults to ACTIVE
is_default_for_task: {TRUE|FALSE}, defaults to FALSE

• Apply current model spec in model templates
  
  ("Other" models like DeiT is not specified here)

• Add unit & integration tests

  • Each task should have 1 SPEED & 1 ACCURACY models, and optionally 1 BALANCE models
  • Each task should have 1 default model, which should be ACTIVE and not in OTHER category
  • Deprecated models should be in OTHER category

How to test

• CI tests

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]

Will this PR be merged after Geti side test?

[goodsong81]

Will this PR be merged after Geti side test?

This change will not affect Geti's model configurations for now. Rather, Geti will implement new model template loading after this change is merged to Geti.

[jaegukhyun]

Will this PR be merged after Geti side test?

This change will not affect Geti's model configurations for now. Rather, Geti will implement new model template loading after this change is merged to Geti.

Should this PR target release branch?

[goodsong81]

Will this PR be merged after Geti side test?

This change will not affect Geti's model configurations for now. Rather, Geti will implement new model template loading after this change is merged to Geti.

Should this PR target release branch?

No, it's not. DeiT is, fortunately, being registered as "Other" model automatically so that we don't need to hurry this change for OTX1.4->Geti1.8. I'm targeting the develop branch on purpose.

[eunwoosh]

Thanks for your work! I left some comments. Please take a look.