[Security Solution][Detections] Leading or trailing whitespace in exception entries is trimmed for display

[marshallmain]

Kibana version:
7.9.0

Describe the bug:
Exception entries with leading or trailing whitespace trim the whitespace when displayed in the UI, even though the whitespace is included in the entry in the backend and therefore also included in queries built from the exception entry. This makes it so the exception entry that executes can be different from what appears in the UI.

Steps to reproduce:

1. Create an exception entry for a rule with trailing whitespace in the exception value e.g.

{
  "field": "rule.name",
  "type": "match_any",
  "value": [
    "PowerShell with Unusual Arguments   "
  ],
  "operator": "included"
}

2. Observe that the UI reports the value as "PowerShell with Unusual Arguments" but the exception only filters documents that have "PowerShell with Unusual Arguments "

Expected behavior:
The UI should display the leading or trailing whitespace as well, or perhaps a warning if there is whitespace that isn't being displayed (newlines or invisible characters might be tricky to display).

Any additional context:
https://github.com/elastic/sdh-security-team/issues/53

[rylnd]

@yctercero I'm assigning this to @qcorporation as an opportunity for new team members to get familiar with our processes.

[rylnd]

Unassigning as the AWP team ended up working on other bugs during their onboarding.

[peluja1012]

Fixed by #139617