choco_packages: split config into a list

[pix]

I modified the default config to allow splitting of choco_packages.

This idea is to allow to pass options to each package directly (to disallow checksums, specify package options, etc.)

[Svieg]

Me and @obilodeau talked about putting those packages in the default profile and install them using the package option in the profile. What do you think?

[pix]

I thought about it but I found that the "package" section of the profile a little cumbersome to use.
I find "package": [{"package": "thunderbird"}], is a little bit verbose.

"package": [
    // Feels hackish
    {"package": "npcap --package-parameters /winpcap_mode=yes"}
    // Feels verbose
    {"package": "thunderbird", parameters: ["/winpcap_mode=yes"], ignore_checksum: true} 
    // Incompatible
    "npcap --package-parameters /winpcap_mode=yes"
],

But I'm not opposed to migrating completly.
Also the patchset now allows to not install chocolatey, maybe moving to profile-example.js and adding a enable_chocolatey (do we need to install it if we don't need packages ?, how to install it without installing any packages ?)

[obilodeau]

The profiles API is marked as experimental on purpose. The package: [ {"package", ... }, ...] is a redundancy I want to get rid of but due to conference release deadlines, I didn't do.

Proposal:

"packages": [ "thunderbird", "npcap --package-parameters /winpcap_mode=yes"];

and we keep "choco_packages" as is for now.

p.s.: note the s on packages