Add vendor specific hook to populate management port status in STATE_DB

[lotus-nexthop]

Why I did it

Nexthop's platforms have an unmanaged switch sitting between the front panel rj45 and the CPU's eth0.
As a result eth0's link state as advertised by the kernel (/sys/class/net/eth0/operstate), does not reflect the state of the rj45.

e.g.

Front Panel RJ45 (Management Port)
         |
        A
         |
    BCM53134 Switch (management switch running in unmanaged mode)
       /    \
      B      C
     /        \
    BMC    CPU (eth0)

Link A may be down (if RJ45 for example is unplugged), but link C (/sys/class/net/eth0/operstate) still says up.

Work item tracking

• Microsoft ADO (number only):

How I did it

Use get_management_port_link_status_override from sonic platform API introduced by sonic-net/sonic-platform-common#654 to populate the management port link state to STATE_DB. This will reflect the correct link state in SNMP (or any future consumers of this state).

How to verify it

Note this requires sonic-net/sonic-platform-common#654 and the platform dependent implementation of it.

admin@gold230:~$ sonic-db-cli CONFIG_DB HSET 'MGMT_PORT|eth0' admin_status up
0
admin@gold230:~$ sudo sonic-db-cli STATE_DB HGET 'MGMT_PORT_TABLE|eth0' oper_status
up

Now I log into management switch to bring the port down. After a minute when monit runs we see on the console:

admin@gold230:~$ sudo sonic-db-cli STATE_DB HGET 'MGMT_PORT_TABLE|eth0' oper_status
down

Which release branch to backport (provide reason below if selected)

• 202305
• 202311
• 202405
• 202411
• 202505
• 202511

Tested branch (Please provide the tested image version)

Description for the changelog

Link to config_db schema for YANG module changes

A picture of a cute animal (not mandatory but encouraged)

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[yxieca]

/azpw ms_conflict

[lotus-nexthop]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).