Add Chip Over Bluez Implementation

[yunhanw-google]

-- Implement CHIPBluezHelper based upon the Thread Bluez Gio code from
openthread.
-- Implement BLEManager and corresponding state machine and event
handling module.
-- Implement TestCHIPoBLEStackMgr test
-- Current code suport CHIPoBLE peripheral mode.
-- Validated via repeatedly creating BLE connection, CHIP BTP communication via characteristic C1
and C2

Fix #2025

[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
[Unmapped],0,1
.debug_line,0,-5

[github-actions]

Size increase report for "nrfconnect-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.elf and ./pull_artifact/chip-nrf52840-lock-example.elf:

sections,vmsize,filesize

[github-actions]

Size increase report for "linux-example-build"

File	Section	File	VM
chip-standalone-demo.out	.eh_frame	8	8
chip-standalone-demo.out	.text	-32	-32

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
.debug_info,0,332
.debug_str,0,135
.debug_abbrev,0,35
[Unmapped],0,21
.strtab,0,19
.debug_macro,0,14
.eh_frame,8,8
.text,-32,-32
.debug_ranges,0,-48
.debug_line,0,-86
.debug_loc,0,-550

[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

[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

[andy31415]

should we have a github issue for these TODOs? Thinking of a TODO format like

TODO(#issueid): ....

so that they are tracked and also greppable when we fix them

[yunhanw-google]

Yep, I would address it when adding bluez central support where there are multiple ble connection. #2027

[yunhanw-google]

@BroderickCarlin / @saurabhst / @jelderton ?
Thanks