zpc: Import libs2 changes from latest snapshot and tag version

[rzr]

Bug-SiliconLabs: SWPROT-9361

API breakage observed, I will issue a PR to reproduce

cc: @silabs-aydogane

Related changes to be merged in following order:

• libs2: Update references for next release (batch 1) #51
• s2: Catch up applications/zpc/components/zwave/zwave_transports/s2/libs/zw-libs2/TestFramework  #57
• libs2/tf: Fix a/z/c/z/z/s/l/z/T/cmock submodule to v2.5.3-g9d092898 #59
• libs2: zwave_transports: Align libs2 API in zwave_s2_transport.c (#51) #52
• SWPROT-9246: "NLS Node List Get/Report" implementation #53
• SWPROT-9320 Controller NLS state storage #54 (not s2)

check NEWS.md file for tracking context

For the record I observe the only changes with

 diff -BurN  -x .git   ./applications/zpc/components/zwave/zwave_transports/s2/libs/zw-libs2/  ~/mnt/zw-libs2/  | \diffstat
 .gitignore               |   20 ++++++++++++++++++++
 .gitmodules              |    3 +++
 Jenkinsfile              |  109 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 sonar-project.properties |   19 +++++++++++++++++++
 4 files changed, 151 insertions(+)
``

[rzr]

@silabs-aydogane job is done, we might want to tag a version just before the refactoring, would this makes sense to you ?

[silabs-aydogane]

@silabs-aydogane job is done, we might want to tag a version just before the refactoring, would this makes sense to you ?

Ok let's do it.

[rzr]

@silabs-aydogane job is done, we might want to tag a version just before the refactoring, would this makes sense to you ?

Ok let's do it.

I will wait the first refactoring change to be ready to merge, lets track that release task:

#63

One remark before closing, maybe we will have to consider about code formatting rules, zpc/unify is using clang format and libs2 code to be formatted using uncrustify... this divergence could be annoying, feel free to file an issue when needed.