Updated T128_peer_path Tags

[shriyanshk128T]

Description

After running the MonitoringAgentCommands Robot, it was identified that there was a shortcoming in the plugin where there was one field that was missing and one field's name was different.

Testing

• Robot Testing

Data we were sending before this PR and the Data it expects

'peer-path-state,adjacentAddress=172.16.3.2,deviceInterface=11,host=t271-dut1.openstacklocal,networkInterface=intf11,node=test1,routerName=combo2,vlan=0 enabled=true,status="UP" 1697668402000000000\n'

peer-path-state, adjacentHostname=([^\,\s]+), deviceInterface=([^\,\s]+), host=([^\,\s]+), networkInterface=([^\,\s]+), peer-path=([^\,\s]+), peerRouter=([^\,\s]+), vlan=([^\,\s]+), status=([^\,\s]+), enabled=([^\,\s]+)

Verify t128_peer_path file output :: Verify the t128_peer_path con... | PASS |
------------------------------------------------------------------------------
MonitoringAgentCommands :: Verify the Monitoring Agent's basic com... | PASS |