[Mellanox] Change NVIDIA SDK build to cmake method and Update SAI, SDK and FW Versions

[dprital]

Why I did it

Up to now, building Mellanox SDK debian packages was done by "autotools" method.
Lately, Mellanox SDK team added the support to build by "cmake" method.
The benefit of using "cmake" is with decrease time of SDK build as "cmake" make it faster then "auto build".

When moving to "cmake" method, all SDK debians:

• applibs
• sx-complib
• sx-example
• sx-gen-utils
• sx-scew
• sxd-libs
• python-sdk-api
• sx-acl-helper
• wjh-libs
• sx-hash-calc
• sx-obj-desc-lib
• sxd-libs

will be replaced by single debian - sys_sdk.

In addition, Update:

• SAI to version 2405.29.0.0
• SDK/FW 4.7.1338/2014.1338

Work item tracking

• Microsoft ADO (number only):

How I did it

• Update cmake version on sonic slave dockers (bookworm and bullseye)
• Change SDK Makefiles, delete all Makefiles of removed debians and add new Makefile for building sys_sdk.
• Change sdk.mk and sdk.dep acordingly.
• sx-kernel package was remain since it is consumed by the host as well and I didn't want to consume sys_sdk in host.

How to verify it

• Enter syncd docker and verify the list of SDK packages are sx-kernel and sys-sdk only
• Run regression tests and verify there is no degradation
• Install the debian that include dbg-symbols and verify there are debug symbols by setting relevant breakpoints
• Test the build time when using "cmake" for building SDK packages, compare to "auto build"

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

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

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)

[dprital]

/azpw run

[mssonicbld]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[bingwang-ms]

The SDK/SAI change LGTM. Need build team to review the cmake related change. @liushilongbuaa Can you please help review?

[bingwang-ms]

@dprital I suggest separating the PR into two PRs, one for SAI/SDK change, and the other one for cmake related change. Please let me know how do you think. Thanks