[DeviceLayer] Add SetupPinCode and SetupDiscriminator to configuration manager

[erjiaqing]

Problem

Current, configuration manager still uses PairingCode and missing SetupDiscriminator, which is required to generate QR code and BLE advertisement.

Solution

Modify configutation manager to include them.

fixes #1654

[erjiaqing]

@gjc13 PTAL

[woody-apple]

@erjiaqing FYI, builds fail

[vivien-apple]

Sorry If I'm confused here. By setup pin code you mean the manual pairing code ? If that's correct the renaming is a bit confusing since the manual pairing code contains a field named.. pin code, that is called in the codebase setUpPinCode (https://github.com/project-chip/connectedhomeip/blob/master/src/setup_payload/ManualSetupPayloadGenerator.cpp#L37)

[erjiaqing]

Setup Pin Code is for setUpPinCode in codebase, the 27bit integer.

[vivien-apple]

Good. I'm less confused then !

In this case, the valid range is between 0 and 134217727 (2^27-1) and 0x0 is normally used to specify that the device has already been paired (for device that supports dynamic generation of QRCode).

And the comments above says that this string is expected to end with a valid Verhoeff check character. But this part of the comment refers to the whole Pairing Code, not the setup pin code afaict.

[erjiaqing]

Oh, I forget to remove that, thanks.

I remembered that the spec said the pin code printed on the device is a 8 digit number, thus 99999999 requires 27 bits, although 27 bits can represent 1.3e9 in fact. I guess device with screen which can display a QR code should also follow this limit.

As for the 0x0, since 0x0 will never be a valid pin code (since it indicate the device is already paired in some case), I think it is also ok if 0x0 means not to use the default value.

However, I wonder if using 0x0 to disable default discriminator is a good choice since discriminator is just a 12bit random number.

[github-actions]

Size increase report for "gn_nrf-example-build"

File	Section	File	VM

Full report output

BLOAT REPORT

Files found only in the build output:
    report.csv

[github-actions]

Size increase report for "gn_linux-example-build"

File	Section	File	VM

Full report output

BLOAT REPORT

Files found only in the build output:
    report.csv

[github-actions]

Size increase report for "nrf-example-build"

File	Section	File	VM

Full report output

BLOAT REPORT

Files found only in the build output:
    report.csv

Comparing ./master_artifact/chip-nrf52840-lock-example.out and ./pull_artifact/chip-nrf52840-lock-example.out:

sections,vmsize,filesize
.debug_info,0,596
.debug_str,0,524
.debug_loc,0,102
.debug_line,0,55
.debug_frame,0,36
.debug_aranges,0,16
.debug_ranges,0,16
[Unmapped],0,-2
.debug_macro,0,-11

[github-actions]

Size increase report for "linux-example-build"

File	Section	File	VM

Full report output

BLOAT REPORT

Files found only in the build output:
    report.csv

Comparing ./master_artifact/chip-standalone-demo.out and ./pull_artifact/chip-standalone-demo.out:

sections,vmsize,filesize

[github-actions]

Size increase report for "esp32-example-build"

File	Section	File	VM

Full report output

BLOAT REPORT

Files found only in the build output:
    report.csv

Comparing ./master_artifact/chip-wifi-echo.elf and ./pull_artifact/chip-wifi-echo.elf:

sections,vmsize,filesize
.debug_info,0,8787
.debug_str,0,468
.debug_line,0,398
.debug_frame,0,48
.debug_aranges,0,16
.debug_ranges,0,16
[Unmapped],0,-5

[woody-apple]

@saurabhst @jelderton @BroderickCarlin ?