Handle community packages better

[Ana06]

Details

The current config include the community!package dotnet3.5. I think we do not display this package in the installer UI or allow to add other community packages. We could have some thing like a text box for these packages (for example comma separated list) and a validation similar to the one in commando VM:

[sara-rn]

I have started with the implementation, I would suggest having 2 buttons (Find Choco Package and Find FLARE-VM Package) that would display 2 different windows, one for Choco packages exactly like in Commando-VM and another one for additional packages from FLARE-VM that are not displayed in the main categories Window (we are not displaying Commando-VM categories). If an additional package is selected, regardless of the source (chocolatey community or FLARE-VM), we cannot add the selection to the main panel of packages grouped by categories. In Commando-VM the packages are listed in a textbox therefore they simply add a new entry with the package added. In the FLARE-VM installer we have checkboxes that are generated dynamically and it might be to difficult to add new checkboxes at the end of the panel. If we display packages serched maually we would need to add a new category for these such as Other or Choco. The easiest way to display manually searched packages would be create a textbox with a label: Additional Packages below. I would also make the panel of Categories smaller if we decide to create this Additional Packages textbox. @Ana06 let me know what your thoughts are

[Ana06]

@sara-rn my original proposal is just to add a texbox with verification where the user can write a list of packages:

[Reset] [Select All] [Deselect All]

FLARE-VM uses Chocolatey packages. You can add extra [Community packages](https://community.chocolatey.org/packages) and [VM-Packages](https://github.com/mandiant/VM-Packages/wiki/Packages).

Extra packages: [package1, package2, package3]

With packages verification I mean looking for the packages in the list in the vm-packages and community feed and providing feedback to the user, for example in the two following ways:

• showing a green/red check and/or explanation below the textbox after it is modified
• when pressing continue, showing an error if it is invalid and not allowing to continue

[sara-rn]

@Ana06 I suggested searching them separately for 2 reasons:

• vm-packages need to end with .vm. Otherwise when searching packages we cannot use the --exact switch in choco search. A .vm can be appended but only if the textbox applies to vm packages.
• to search vm-packages with choco search we need to provide a remote repository (with -s)
• to search choco community packages we do not need to provide the switch

[Ana06]

@sara-rn we are only verifying them in the list and the name should be exact. You can call choco search twice without exposing this to the user.