Fix Whitelist buttons on query log pages

[sgtlaggy]

By submitting this pull request, I confirm the following:

• I have read and understood the contributors guide, as well as this entire template.
• I have made only one major change in my proposed changes.
• I have commented my proposed changes within the code.
• I have tested my proposed changes.
• I am willing to help maintain this change if there are issues with it later.
• I give this submission freely and claim no ownership.
• It is compatible with the EUPL 1.2 license
• I have squashed any insignificant commits. (git rebase)
• I have Signed Off all commits. (git commit --signoff)

---

What does this PR aim to accomplish?:
Fix the behavior of the Whitelist button on both the short-term and long-term query log pages.
Previously, domains blocked due to cases

• 5 (exact blacklist),
• 9 (gravity),
• 10 (regex blacklist CNAME), and
• 11 (exact blacklist CNAME)

would blacklist the domain instead of whitelisting it when clicking the Whitelist button.

How does this PR accomplish the above?:
It corrects a typo of data[5] by using array.indexOf instead of several === checks. If === would be preferable, I can change that upon request.
It also corrects the omission of 3 whitelist buttons from the click event, which erroneously blacklisted a domain when clicking the "Whitelist" button.

What documentation changes (if any) are needed to support this PR?:
None

[sgtlaggy]

Neglected to mention in commit (for auto close), this should close #1348 and maybe #1533.

[PromoFaux]

I seem unable to reproduce the problem that this PR is designed to fix...

I have tried on both current master and current devel, and in both cases pressing whitelist correctly adds to the whitelist

I might need @DL6ER's eyes on this one please...

[DL6ER]

This PR specifically fixes the whitelisting button for the recently added deep CNAME inspection blocking types. In addition, it fixes checking the wrong field for exactly blacklisted domains.

[DL6ER]

@sgtlaggy I edited your description slightly as status 5 is exact black-, not whitelist. From your PR it is clear that this was merely a typo.