Re-design Vulnerability details page

[ameliav]

🗣 Description

Re-design the current Vulnerability details page. Completes issues: #2306, #2307, #2308, #2309

💭 Motivation and context

Change makes for a better user interface for the Vulnerability details page.

🧪 Testing

✅ Pre-approval checklist

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

✅ Pre-merge checklist

• Revert dependencies to default branches.
• Finalize version.

✅ Post-merge checklist

• Create a release.

[schmelz21]

@ameliav , upon review please remove the CWE Name reference and move forward with merging the Vuln details page in its current state. We will Issue separate tickets to support the notes section and the CWE name. They both require more detailed planning.

[cduhn17]

See comments

[rapidray12]

Some of the TODO comments in the code are a bit disconcerting (e.g. //TODO: change this to something else??)

[Matthew-Grayson]

Some of the TODO comments in the code are a bit disconcerting (e.g. //TODO: change this to something else??)

Understandable. There are just a few things about the new tables that don't match the rest of the code base. The column names for one thing use snake case instead of camel case. This adds confusion to development when displaying detailed information from API responses. I think we should make these changes before the new tables are deployed to production.

I'll create an issue and link it.

[Matthew-Grayson]

@cduhn17 @rapidray12 TODOs captured here.
#2521
#2522
#2523
#2524

[nickviola]

LGTM

[schmelz21]

LGTM - One comment, on TODOs moving forward, I believe it will be required in future reviews to reference the Issue number also in the code.