PluginUtility::ParseCheckOutput(): if it doesn't look like perfdata, it's not perfdata

[Al2Klimov]

fixes #8006

[Al2Klimov]

With this #8006 (comment) has not been broken, but a |lolcat=1 has been handled.

[yhabteab]

Testprotocol:
Until now it was not possible to print ASCII tables in the plugin output. The output looks mixed up and the table was barely recognizable.

"output": "special tables
   +---------------+---------------------+-----+------------------------------------------------------------------------------------------------------+

    +---------------+---------------------+-----+------------------------------------------------------------------------------------------------------+

 ┌───────────────┬─────────────────────┬─────┬──────────────────────────────────────────────────────────────────────────────────────────────────────┐
 │ CVE-2018-6533 │ 2018-02-27 19:29:00 │ 7.2 │ An issue was discovered in Icinga 2.x through 2.8.1. By editing the init.conf file, Icinga 2 can be  │
 │               │                     │     │ run as root. Following this the program can be used to run arbitrary code as root. This was fixed by │
 │               │                     │     │ no longer using init.conf to determine account information for any root-executed code (a larger      │
 │               │                     │     │ issue than CVE-2017-16933).                                                                          │
 └───────────────┴─────────────────────┴─────┴──────────────────────────────────────────────────────────────────────────────────────────────────────┘

This functionality has now been implemented and is ready for you to use.

"output": "special tables 
 +---------------+---------------------+-----+------------------------------------------------------------------------------------------------------+
 | CVE-2018-6533 | 2018-02-27 19:29:00 | 7.2 | An issue was discovered in Icinga 2.x through 2.8.1. By editing the init.conf file, Icinga 2 can be  |
 |               |                     |     | run as root. Following this the program can be used to run arbitrary code as root. This was fixed by |
 |               |                     |     | no longer using init.conf to determine account information for any root-executed code (a larger      |
 |               |                     |     | issue than CVE-2017-16933).                                                                          |
 +---------------+---------------------+-----+------------------------------------------------------------------------------------------------------+


 ┌───────────────┬─────────────────────┬─────┬──────────────────────────────────────────────────────────────────────────────────────────────────────┐
 │ CVE-2018-6533 │ 2018-02-27 19:29:00 │ 7.2 │ An issue was discovered in Icinga 2.x through 2.8.1. By editing the init.conf file, Icinga 2 can be  │
 │               │                     │     │ run as root. Following this the program can be used to run arbitrary code as root. This was fixed by │
 │               │                     │     │ no longer using init.conf to determine account information for any root-executed code (a larger      │
 │               │                     │     │ issue than CVE-2017-16933).                                                                          │
 └───────────────┴─────────────────────┴─────┴──────────────────────────────────────────────────────────────────────────────────────────────────────┘

[julianbrost]

Should only improve the behavior, even though it's still some heuristic and you'll still be able to construct cases where this doesn't help. But a perfect solution probably doesn't exist anyways, as there seems to be no intended way to include | in the output.