Adds changes to RecommendationItem enum to accomodate MIG strings

[bharathappali]

Description

This PR is fourth part of the set of PR's which will be raised for adding GPU support #1312

This PR adds changes to RecommendationItem enum to accomodate MIG strings

This PR is build on top of #1317, so it needs to be merged after merging #1317

Fixes #1312

Type of change

• Bug fix
• New feature
• Docs update
• Breaking change (What changes might users need to make in their application due to this PR?)
• Requires DB changes

How has this been tested?

Tests will be added in the subsequent PR

• New Test X
• Functional testsuite

Test Configuration

• Kubernetes clusters tested on:

Checklist 🎯

• Followed coding guidelines
• Comments added
• Dependent changes merged
• Documentation updated
• Tests added or updated

Additional information

None

[dinogun]

@bharathappali Needs to be rebased against mvp_demo

[bharathappali]

Apologies for the overlook, I have rebased to mvp_demo. Thanks @dinogun

[dinogun]

@bharathappali Please rebase as I've merged your earlier PRs

[bharathappali]

Sure, I have rebased to latest mvp_demo @dinogun .

[dinogun]

LGTM

[dinogun]

@bharathappali The crc PR check is failing. Looks like some tests need to be updated with the new CONSTANTS

[bharathappali]

@dinogun Yes we need the adapter for the recommendation item enum, as the changes are getting lengthy I have added them in subsequent PR's

[bharathappali]

@dinogun As there is no adapter the keys in recommendation are changed in this way

"variation": {
                            "requests": {
                              "MEMORY": {
                                "amount": 187.98999999999998,
                                "format": "MiB"
                              },
                              "CPU": {
                                "amount": -0.17000000000000015,
                                "format": "cores"
                              }
                            },
                            "limits": {
                              "MEMORY": {
                                "amount": 138.2,
                                "format": "MiB"
                              },
                              "CPU": {
                                "amount": 0.42999999999999994,
                                "format": "cores"
                              }
                            }
                          },

This will be fixed in #1321

[dinogun]

Merging with the assumption that PR #1321 will fix the test failures