Integrate OEM launchpad tags into QABro

[Kristin Chuang]

Past discussions for reference: https://docs.google.com/document/d/1_mZGHJzXUwV6-hq2SZjDKed2xcX3Um5-Pqy0XXuLe4I/edit#heading=h.4lu4w12akx1h

As stated in the link above:
* Step 1: QA design how tagging in QAbro works
* Step 2: SWE/QA redesign the tags.json file structure which stores all tags that are to be included into QAbro

This bug is for Step 1: Have QAbro include a feature that allows users to select multiple OEM launchpad tags when filing a bug.

=========================================================================

[Possible tagging logic & UI]
Option 1:
  QA selects tags directly
  (a) show all available tags grouped in some way for users to select
  (b) hierarchical tags :
      e.g. user selects “wifi” > QAbro then shows available “ihv”s

Option 2:
  QA selects a category (like the current QAbro implementation)
  > QAbro maps that category to a certain tag + auto detects current HW
  > QAbro adds tags “wifi” & “ihv-redpine”

Option 3: ?

[Pierre Equoy (pieq)]

Implemented in proposed Merge Request above.

I went with the easiest solution for now: 2 columns of tags, "Impacted Feature(s)" and "Impacted Vendor(s)", that can be manually selected by the user.

User can select as many as required (in the previous versions of QABro, it was a radio button, so only one feature could be selected, but now these are checkboxes so you can select multiple items).

Selecting/Deselecting a feature or a vendor updates the list of tags above (see screenshot), while leaving the manually entered tags intact.