[Dualtor] add support for neighbor mode in golden_config

[harjotsinghpawra]

Description of PR

Summary:
neighbor_mode knob was added in MUX_CABLE,now we needed an option to run mgmt runs with neighbor mode set as host-route or prefix-route for any run on dualtor.

How to enable it :

conf-name: docker-ptf
group-name: sonic_cisco
topo: t0
ptf_image_name: docker-ptf-titan
prober_type: hardware
neighbor_mode: prefix-route
ptf: docker-ptf
ptf_ip: 192.168.122.78/24
ptf_ipv6: fc0b::1/64
server: server_1
vm_base: VM0100
dut:
titan-01
inv_name: lab
auto_recover: 'True'
comment: Test ptf titan

Summary:
Fixes # (issue)

Type of change

• Bug fix
• [X ] Testbed and Framework(new/improvement)
• New Test case
  • Skipped for non-supported platforms
• Test case improvement

Back port request

• 202311
• 202405
• 202411
• 202505
• 202511
• 202512
• 202605

Tracking issue/work item for backport/cherry-pick request:
Failure type:

Approach

What is the motivation for this PR?

Support for neighbor_mode was added as part of following PR
sonic-net/sonic-swss#4152

Needed a knob for dualtor setups to use one setting always to test it

How did you do it?

Added a new knob in testbed.yaml which will only be active for dualtor testbeds
and add neighbor_mode to golden_config_db.json

How did you verify/test it?

Ran on local setup

Any platform specific information?

By default its set to host-route which is supported by all platforms

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

dualtor

Documentation

sonic-net/SONiC#2176

[mssonicbld]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[zjswhhh]

/azpw run

[mssonicbld]

⚠️ Notice: /azpw run only runs failed jobs now. If you want to trigger a whole pipline run, please rebase your branch or close and reopen the PR.
💡 Tip: You can also use /azpw retry to retry failed jobs directly.

Retrying failed(or canceled) jobs...

[mssonicbld]

Retrying failed(or canceled) stages in build 1148923:

✅Stage Test:

• Job impacted-area-kvmtest-t1-lag-vpp by Elastictest: retried.
• Job impacted-area-kvmtest-t1-lag by Elastictest: retried.

[zjswhhh]

Hi @bingwang-ms - please help review.

[prsunny]

Approving for 202605 since this is planned to be the default config for Dualtor
@vaibhavhd , @yxieca , @lolyu for viz cherry-pick

[mssonicbld]

@harjotsinghpawra PR conflicts with 202605 branch

[zjswhhh]

Hi @harjotsinghpawra -can you raise a PR to 202605 to manually pick up this change?

[harjotsinghpawra]

@zjswhhh Hi Jing actually this PR needs to go first
#20765

[mssonicbld]

This PR is approved for branch 202605. No cherry pick PR has been created because of code conflict. @harjotsinghpawra, please manually create the cherry pick PR.
If this change is already in 202605, please comment "already in 202605". Thanks!

_{---Powered by SONiC BuildBot}

[zjswhhh]

@zjswhhh Hi Jing actually this PR needs to go first #20765

Hi @harjotsinghpawra - can you raise a PR to 202605 to manually cherry-pick both?

[zjswhhh]

@zjswhhh Hi Jing actually this PR needs to go first #20765

Hi @harjotsinghpawra - can you raise a PR to 202605 to manually cherry-pick both?

Hi @harjotsinghpawra - nvm I raised it already, please help review.

[mssonicbld]

This PR has backport request label(s) for branch(es): 202605, but is missing required test information. Please make sure you tick the tested branch(es) in the Tested branch section and provide test evidence (e.g., 202605: <test result>) in the Test result section as well in your PR description.

_{---Powered by SONiC BuildBot}