refactor: add separate table to store system-cve statuses

[jdobes]

Secure Coding Practices Checklist GitHub Link

• https://github.com/RedHatInsights/secure-coding-checklist

Secure Coding Checklist

• Input Validation
• Output Encoding
• Authentication and Password Management
• Session Management
• Access Control
• Cryptographic Practices
• Error Handling and Logging
• Data Protection
• Communication Security
• System Configuration
• Database Security
• File Management
• Memory Management
• General Coding Practices

[jira-linking]

Commits missing Jira IDs:
87d1bab
Referenced Jiras:
https://issues.redhat.com/browse/RHINENG-2328

[codecov-commenter]

Codecov Report

Attention: 3 lines in your changes are missing coverage. Please review.

Files	Coverage Δ
common/peewee_model.py	96.57% <100.00%> (+0.09%)	⬆️
manager/cve_handler.py	94.28% <100.00%> (+0.01%)	⬆️
manager/filters.py	96.14% <100.00%> (-0.02%)	⬇️
manager/system_handler.py	98.87% <100.00%> (+<0.01%)	⬆️
manager/vulnerabilities_handler.py	92.30% <100.00%> (+0.03%)	⬆️
taskomatic/jobs/cacheman.py	0.00% <ø> (ø)
taskomatic/jobs/usage_metrics.py	99.32% <ø> (ø)
vmaas_sync/vmaas_sync.py	93.05% <100.00%> (+0.04%)	⬆️
manager/admin_handler.py	68.09% <0.00%> (-0.27%)	⬇️
manager/status_handler.py	95.77% <97.75%> (+4.77%)	⬆️

📢 Thoughts on this report? Let us know!

[yungbender]

I like it, it is pretty good. It is a nice change that the 0 value statuses are implicit and not stored inside the table.

One more question, don't you wanna drop the columns in system_vulnerabilities table? Or are we just keeping it to being able to roll it back?

I will also test it locally, before merging.

[jdobes]

I'd keep status columns in system_vulnerabilities if we need to rollback. Let's delete it later.