Add new HwSKUs for Arista-7060dx5-32

[bobbymcgonigle]

Why I did it

New desired configurations on this Arista SKU

Work item tracking

• Microsoft ADO (number only):

How I did it

Added the hwsku folders with the necessary files to populate config_db

How to verify it

change default sku and generate a new config_db.json

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

• 201811
• 201911
• 202006
• 202012
• 202106
• 202111
• 202205
• 202211
• 202305
• 202311

Tested branch (Please provide the tested image version)

• 202305

Description for the changelog

Link to config_db schema for YANG module changes

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

[zhenggen-xu]

Can you add buffer/qos config files similar to Arista-7060DX5-32 to the new HWKSUs?

[zhenggen-xu]

Is it possible to use the same th4XXX.bcm file for both HWSKUs? We should make the bcm file agnostic to HWSKUs, and let SONiC SAI APIs to add/delete ports during the initialization, this will make future HWSKU creation straightforward.

[bobbymcgonigle]

Is it possible to use the same th4XXX.bcm file for both HWSKUs? We should make the bcm file agnostic to HWSKUs, and let SONiC SAI APIs to add/delete ports during the initialization, this will make future HWSKU creation straightforward.

Unfortunatly this is not available in 202305 (where we would like this to go) due to CSP case CS00012347969. This is fixed in SAI 9.

Until 202305 moves to that SAI version we cannot support the single bcm file.

Can you add buffer/qos config files similar to Arista-7060DX5-32 to the new HWKSUs?

We are planning to do this in a seperate PR. For now we would like to get these hwsku's merged to unblock testing with these front panel configurations.

[zhenggen-xu]

LGTM.