Add Basic cluster tests for attributes constraints

[vivien-apple]

Problem

There is no specific tests for the Basic cluster.

Change overview

• Move the Basic cluster definition out of the Silabs's definition and update it a little
• Add Test_10_1_1 for the Basic cluster
• Update the templates to support optional keyword, such that an attribute is tested only if it is supported on the accessory side
• Update the templates to support constraints keyword
• Add minLength/maxLength constraints support (format and type still needs to be done)
• Update gen/ folders

Testing

• Tests were generated for the Darwin CI and the test suites using chip-tool

[woody-apple]

@Damian-Nordic @jepenven-silabs ?

[bzbarsky-apple]

Looks good, but @tcarmelveilleux's comment about the max length there should be addressed, either here or in a followup.

[woody-apple]

@vivien-apple conflicts :(

[andy31415]

Needs conflict resolution.

Cannot easily review this due to large amoung of generated code.

[github-actions]

Size increase report for "esp32-example-build" from 42c2ccd

File	Section	File	VM
chip-all-clusters-app.elf	.flash.text	-24	-24
chip-all-clusters-app.elf	.flash.rodata	-224	-224
chip-all-clusters-app.elf	.dram0.bss	0	-472

Full report output

BLOAT REPORT

Files found only in the build output:
    report.csv

Comparing ./master_artifact/chip-pigweed-app.elf and ./pull_artifact/chip-pigweed-app.elf:

sections,vmsize,filesize

Comparing ./master_artifact/chip-all-clusters-app.elf and ./pull_artifact/chip-all-clusters-app.elf:

sections,vmsize,filesize
[Unmapped],0,224
.debug_ranges,0,24
.debug_abbrev,0,23
.debug_str,0,2
.debug_loc,0,-4
.flash.text,-24,-24
.debug_line,0,-46
.debug_info,0,-67
.flash.rodata,-224,-224
.dram0.bss,-472,0

[github-actions]

Size increase report for "gn_qpg6100-example-build" from 42c2ccd

File	Section	File	VM
chip-qpg6100-lighting-example.out	.heap	0	32
chip-qpg6100-lighting-example.out	.bss	0	-32
chip-qpg6100-lighting-example.out	.text	-32	-32

Full report output

BLOAT REPORT

Files found only in the build output:
    report.csv

Comparing ./master_artifact/chip-qpg6100-lighting-example.out and ./pull_artifact/chip-qpg6100-lighting-example.out:

sections,vmsize,filesize
.heap,32,0
[Unmapped],0,32
.debug_ranges,0,24
.debug_abbrev,0,23
.debug_str,0,-8
.debug_line,0,-20
.bss,-32,0
.text,-32,-32
.debug_info,0,-71

Comparing ./master_artifact/chip-qpg6100-lighting-example.out.map and ./pull_artifact/chip-qpg6100-lighting-example.out.map:

BLOAT EXECUTION FAILED WITH CODE 1:
bloaty: unknown file type for file './pull_artifact/chip-qpg6100-lighting-example.out.map'

[github-actions]

Size increase report for "nrfconnect-example-build" from 42c2ccd

File	Section	File	VM
chip-lock.elf	[LOAD #3 [RW]]	0	-4
chip-lock.elf	device_handles	-12	-12
chip-lock.elf	rodata	-16	-16
chip-lock.elf	text	-20	-20
chip-lock.elf	bss	0	-28

Full report output

BLOAT REPORT

Files found only in the build output:
    report.csv

Comparing ./master_artifact/chip-lock.elf and ./pull_artifact/chip-lock.elf:

sections,vmsize,filesize
.debug_ranges,0,24
.debug_abbrev,0,23
.debug_loc,0,5
.debug_str,0,-1
[LOAD #3 [RW]],-4,0
device_handles,-12,-12
rodata,-16,-16
.debug_line,0,-20
text,-20,-20
bss,-28,0
.debug_info,0,-71

Comparing ./master_artifact/chip-shell.elf and ./pull_artifact/chip-shell.elf:

sections,vmsize,filesize

[bzbarsky-apple]

Cannot easily review this due to large amoung of generated code.

@andy31415 fwiw, reviewing the individual changesets worked pretty well for me for this one....