2521 Refactor CVE and Product Info Tables

[Matthew-Grayson]

🗣 Description

• Refactor column names of cve and product_info tables to camel case
• Rename product_info table to cpe
• Remove redundant cpe_list column.
• Update associated endpoints, joins, API calls, and tests
• Update syncdb populate to include cve and cpe tables

💭 Motivation and context

We recently added two tables, cve and product_info. The column names follow a different naming convention than the rest of the codebase. For one thing they use snake case instead of camel case. This makes our API inconsistent and adds confusion to frontend development.

I renamed the product_info table to cpe so that references to entries are more informative: cpe = single entry and cpes is a collection of entries. This isn't the case now with product_info being used as both singular and plural.

I also removed the cpe_list column since there is already a join table between cves and cpes coded into the db model.

Closes issue #2534 Closes issue #2521

🧪 Testing

Modified tests for API functionality. Manually tested Vulnerability Details page.

✅ Pre-approval checklist

• [x] This PR has an informative and human-readable title.
• [x] Changes are limited to a single goal - eschew scope creep!
• [x] All future TODOs are captured in issues, which are referenced in code comments.
• [x] All relevant type-of-change labels have been added.
• [x] I have read the CONTRIBUTING document.
• [x] These code changes follow cisagov code standards.
• [x] All relevant repo and/or project documentation has been updated to reflect the changes in this PR.
• [x] Tests have been added and/or modified to cover the changes in this PR.
• [x] All new and existing tests pass.

✅ Pre-merge checklist

• [ ] Revert dependencies to default branches.
• [ ] Finalize version.

✅ Post-merge checklist

• [ ] Create a release.

[Matthew-Grayson]

PR currently includes commits from #2352. I will mark this ready for review once #2352 is merged.

[Matthew-Grayson]

This is difficult to test due to issues calling the PE API today. Let's prioritize adding the new tables to the syncdb populate method to assist local development.

[Matthew-Grayson]

I've updated syncdb's populate method to include the cve and cpe tables to assist local development. To this PR's changes:

1. Run npm run syncdb -- -d dangerouslypopulate
2. Run npm run syncdb
3. Run npm run syncdb -- -d populate
4. Confirm that vulnerability details page populates data properly
5. Confirm that all tests pass