feat: add l1-connect cli for elastictest support

[auspham]

Description of PR

Summary: Add Cli to support L1 connect from pipeline/elastictest
Fixes # (issue) 36011538

Type of change

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

Back port request

• 202205
• 202305
• 202311
• 202405
• 202411
• 202505

Approach

What is the motivation for this PR?

usage: sonic_l1_cli.py [-h] {connect,read} ...

Sonic-mgmt utility command-line to connect ports and read ports from SONiC L1 device.

positional arguments:
  {connect,read}
    connect       Connect to device.
    read          Read from device.

optional arguments:
  -h, --help      show this help message and exit

Usecases:

1. Connect port
../.azure-pipelines/sonic_l1_cli.py connect --device l1_device --port "1,41" -i inventory

This will do the following connection:
    Connect single port
        1A -> 41B
        41A -> 1B

2. Connect port in a combined port group
../.azure-pipelines/sonic_l1_cli.py connect --device l1_device --port "1|2|3|4,41|42|43|44" -i inventory

This will do the following connection:
    Connect port group:
        1A -> 41B
        41A -> 1B
        ...
        4A -> 44B
        44A -> 4B

3. Connect multiple port
../.azure-pipelines/sonic_l1_cli.py connect --device l1_device --port "1,41" --port "2,42" -i inventory

This will do the following connection:
    Connect single port
        1A -> 41B
        41A -> 1B

        2A -> 42B
        42A -> 2B

4. Read the port connection
../.azure-pipelines/sonic_l1_cli.py read --output output_file --device l1_device -i inventory

This will write to output_file
{
    "port_list": [
        "1,43",
        "2,46",
        "17,45",
        "19,47",
        "20,48",
        "21,49",
        "22,50",
        "23,51",
        "24,52"
    ]
}

If you dont want to output to any file, simply omit --output

How did you do it?

How did you verify/test it?

Physical device

Any platform specific information?

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

Documentation

[mssonicbld]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mssonicbld]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mssonicbld]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[wangxin]

If this script is a CLI, it would be better to use sys.exit(<non_zero_value>) when something is wrong.