applying a control tag failure does NOT change the control failures count

[vjeffrey]

Describe the bug

We display a field "control failures" on the nodes list in the Automate UI. This correlates to node.latest_report.controls.failed.total value returned by the api.
When we filter by profile, this number changes to reflect the amount of controls that failed that were part of the selected profile. When we filter by control, this number changes to reflect the status of the selected control on that node (i.e. 1 failed, or passed/skipped).

When filtering by control tag, this number is not modified. I spent a bit of time reading the code yesterday to see about addressing this. It doesn't look like it'll be a simple fix - it basically means introducing a new depth, "control tag filter depth", which would aggregate totals across multiple profiles and controls.
Let's check with @rickmarry to see what the options are on this/brainstorm a bit with the team.

Note: this issue was called out by our CFT that are showing the feature to customers.

To Reproduce

Steps to reproduce the behavior:

• run a scan with a profile that has control tags
• note the total failed controls on that node object
• filter by a control tag
• see the number does not change

Expected behavior

Expect control failure total to reflect the amount of controls that failed on that node that matched the requested tag filter.

Screenshots

Versions (please complete the following information):

• Automate Build Number: 20191007115919

[vjeffrey]

so tl;dr on this issue:

• the number value for failed controls only changes when deep filtering is applied
• deep filtering only works when you filter by one profile or one profile + one control
• the way the data is architected today, we cannot modify the value for failed controls when a control tag filter is applied

we will start looking in earnest at the work needed for these arch changes with #1738