New attributes and object for patch metadata (kb_article)

[jasonbreimer]

Related Issue:

#684

Related PR:

#698

Objective:

This includes attribute and object changes to allow optional enrichment of vulnerability class with patch/update meta data. The new object kb_article replaces an attribute kb_articles and contains additional details regarding the specific patch. This change will allow allow direct mapping of patch "findings" (forthcoming).

Change Details:

1. New attributes: bulletin, classification, cpe, superseded, related_cves
2. New Class: kb_article

Next Steps:

1. New PR for cpe attribute added to product object.
2. New draft PR for new Class in Discover for Patch Findings.

[irakledibm]

"classification" is very generic attribute and may add confusion with "classifications" in our dictionary. probably it is better to call "article_classification" or "kb_classification"?

[floydtree]

"classification" is very generic attribute and may add confusion with "classifications" in our dictionary. probably it is better to call "article_classification" or "kb_classification"?

I am okay with classification for 2 reasons -

1. The confusion will be negated by the contextual use of that field -> kb_article.classification
2. Adding a generic field name will help in reusability of that field down the road

[jasonbreimer]

Yes, that was my thought for classification. I started with something like kb_classification in the dictionary but thought it might be better to create something generic so it could be re-used.

I can go either way!

[irakledibm]

I have no objections then

[jasonbreimer]

Rebuilding branch and PR because of merge conflicts.