PVST feature support

[bendrapubalareddy]

**** Please hold on review, will remove this line once ready for review **********
Changes:
modified: cfgmgr/Makefile.am
new file: cfgmgr/stpmgr.cpp
new file: cfgmgr/stpmgr.h
new file: cfgmgr/stpmgrd.cpp
modified: configure.ac
modified: orchagent/Makefile.am
modified: orchagent/orchdaemon.cpp
modified: orchagent/orchdaemon.h
modified: orchagent/port.h
modified: orchagent/portsorch.cpp
modified: orchagent/saihelper.cpp
new file: orchagent/stporch.cpp
new file: orchagent/stporch.h
new file: swssconfig/sample/00-copp.config.json
modified: tests/mock_tests/Makefile.am

What I did

Why I did it

How I verified it

Details if related

[adyeung]

@bendrapubalareddy BRCM posted the original PVST code PR to the community back in 2019, what is the point of reposting the same? By 2024, the SONiC community has approved and agreed upon MSTP through the SONiC HLD review meetings and PENS WG. The design and scope of this approved MSTP will encompass the requirements of PVST. Reintroducing the PVST code PR at this juncture risks significant conflicts with the upcoming MSTP contributions from BRCM and xFLOW.

[bendrapubalareddy]

@bendrapubalareddy BRCM posted the original PVST code PR to the community back in 2019, what is the point of reposting the same? By 2024, the SONiC community has approved and agreed upon MSTP through the SONiC HLD review meetings and PENS WG. The design and scope of this approved MSTP will encompass the requirements of PVST. Reintroducing the PVST code PR at this juncture risks significant conflicts with the upcoming MSTP contributions from BRCM and xFLOW.

Yes, these are old PRs from BRCM for PVST functionality. It needed some fixes to make it work. There should not be conflicts with MSTP if we are aligned with PVST functionality as per these PRs. We can work together to resolve conflicts if there is any. Could you please share the next meeting of MSTP review, we can join and discuss. I thought today there is meeting, but i did not find an invite.