fix(ui): properly map over queryBuilder tags and set default values

[hoorayimhelping]

Closes HoneyBadger #12

For the purposes of expediency and fixing a terrible prod bug, this bypasses good hygiene like tests. I added an issue to follow up on that.

Error was introduced here.

I initially noticed a lot of duplication of the initial state of tags, so I added the notion of an initial tag. Tags in query builder parlance map to the boxes at the bottom of the query builder. So each query that was built with the builder has an array of tags associated with it. On load, these tags are nulled out to an initial state. Here is a kinda psuedocode explanation of what that looks like:

const initialStateHelperTags = [{
  aggregateFunctionType: 'filter',
  keys: [],
  keysSearchTerm: '',
  keysStatus: RemoteDataState.NotStarted,
  values: [],
  valuesSearchTerm: '',
  valuesStatus: RemoteDataState.NotStarted,
}]

queryBuilder: {
  tags: [
    initialStateHelperTags[0],
    initialStateHelperTags[0],
    initialStateHelperTags[0]
  ]
}

When the query builder loads, it should loop over all the tag groups in the query builder and set them to default values.

What my buggy code did was this:

queryBuilder.tags = initialStateHelperTags

See the differences? It set the array of tags, which maps to each filtered section of a query, to an array with with a single item, the default tag.

big oof.

Testing Instructions:

On master:

1. Create a query with the query builder.
2. Load that query
3. 💥

Checkout this branch:

1. git checkout bs_fix_undefined_tags
2. Load the query you saved before
3. 🎉

• CHANGELOG.md updated with a link to the PR (not the Issue)
• Well-formatted commit messages
• Rebased/mergeable
• Tests pass