Rename "Fixed by vulnerabilities" column

[johnmhoran]

Reference: #1501
Reference: #1520

@pombredanne @TG1999 -- ready for your review.

Note that when I ran make test locally, 1 test, unrelated to my update, failed:

FAILED vulnerabilities/tests/test_github_osv.py::GithubOSVImporter::test_github_osv_importer7 - TypeError: unhashable type: 'Version'

The updated column now looks like this:

[johnmhoran]

@pombredanne @TG1999 Do we want a similar change from Fixed by packages to Fixed packages in the vulnerability UI search results and vulnerability details pages? The context is similar though not identical. If yes, I'll open an issue and make those changes.

[pombredanne]

As discussed in the #1520 issue please use "fixing vulnerabilities" and merge!

• Have consistent labels in UI and API and models for affected and fixed #1520

[pombredanne]

Feel free to also align the CSS class names with the latest and greatest

[johnmhoran]

@pombredanne I have made the change (locally only atm) in the Packages search results page from "Fixed by vulnerabilities" (or yesterday in this PR, "Fixed vulnerabilities") to "Fixing vulnerabilities", e.g.,

I began to make the change you requested to the span class name for the renamed "Fixing vulnerabilities" from affected-fixed to fixing-vulnerabilities. However, checking for usage of that CSS style, I see that I used that one CSS style for all similar column names/references, i.e., it's also used in the Package search results page for the "Affected by vulnerabilities" column, and is used as well in package_details.html, vulnerabilities.html and vulnerability_details.html.

Rather than making two new classes for the package and vuln CSS column and similar references -- with the exact same settings -- for now I am making no change until you've had a chance to consider the current usage. If you'd like me to make separate names for each and rename where needed, please let me know and I'll do that.

But first.... One more related question arises from the current change. The change above is on the Packages search result page, packages.html. If you drill down by clicking one of the packages from the "Package URL" column, you come to the package details page, package_details.html, where we describe in greater detail the same set of relationships summarized in the Package search results page. Do you want any changes to the naming conventions currently used on the details page?

[pombredanne]

Looking good. Merging!