Added Multi-Asic Handling for test_gnmi_configdb_full_01 TC

[agadia-cisco]

Description of PR

Summary: For Multi-Asic devices, test_gnmi_configdb_full_01 TC isn't using asic specific namespace, due to which PORT keys received from get_interface_status & one in config_db are not in sync.

Fixes # (issue)
Checks whether DUT is multi-asic or not; if yes, then generates configuration based on the asic namespace which contains the PORT key returned by get_inerface_status

Type of change

• Bug fix
• Testbed and Framework(new/improvement)
• Test case(new/improvement)

Back port request

• 202012
• 202205
• 202305
• 202311
• 202405

Approach

What is the motivation for this PR?

• Issue 15407 : Multi-asic support for test_gnmi_configdb TCs
• This PR just adds the multi-asic support; but still TC would fail because Multi-Asic support for ApplyPatchDb API has to be provided, Issue link

How did you do it?

Checks whether DUT is multi-asic or not; if yes, then generates configuration based on the asic namespace which contains the PORT key returned by get_inerface_status

How did you verify/test it?

Any platform specific information?

Supported testbed topology if it's a new test case?

Documentation

[agadia-cisco]

cc - @vperumal