Categorize waivers into persistent / temporary

[comps]

The current waivers, https://github.com/RHSecurityCompliance/contest/blob/02e2ea0c64e684e00d4a6df6b2e4ae51d007b050/conf/waivers-upstream , have mostly arbitrary grouping by test/rule, and they contain both

• long-term failures caused by technology limitations, ie. systemd not running in Anaconda environment
• short-term failures caused by a soon-to-be-fixed bug

We should probably split waives explicitly into these (or more) sections within the waiver file, so we don't have to traverse through the long-term list of failures when checking the status of the short-term ones.

Maybe even a section on TODO - unknown, unidentified failures, that are of high priority to be identified, but exist because we want daily productization runs to PASS tomorrow.