Add JS clickable tab link functionality

[johnmhoran]

Reference: #1286

[johnmhoran]

@TG1999 I just finished adding two simple JavaScript-based clickable tab links to the Vulnerability details template. Please give this a close look and let me know if you have any comments, suggestions etc.

I opened this PR and all tests passed, but 2 documentation builds threw a warning, treated as an error, and thus those 2 builds failed. The warnings are identical and have nothing to do with my work -- related to a broken links in importers_link.rst.

Warning, treated as error:
/home/runner/work/vulnerablecode/vulnerablecode/docs/source/importers_link.rst:22:broken link: https://www.debian.org/security/oval/ (403 Client Error: Forbidden for url: https://www.debian.org/security/oval/)
(  importers_link: line   22) 
Error: Process completed with exit code 2.

[johnmhoran]

@TG1999 The errors in the documentation build refer to importers_link.rst, which contains an include for SOURCES.rst, which itself contains a table of importer links (see https://github.com/nexB/vulnerablecode/blob/main/SOURCES.rst), one of which is the link for debian oval -- https://www.debian.org/security/oval/. This currently takes me to

This is similar to the link in /vulnerablecode/vulnerabilities/importers/debian_oval.py -- file_url = f"https://www.debian.org/security/oval/oval-definitions-{release}.xml", which also leads to the same sort of Forbidden page.

Many of the first group of hits in a Google search for debian oval security also lead to a Forbidden page.

It would be interesting to know when the debian_oval importer was last run and whether it encountered the same Forbidden page and threw an error. I assume that if it were to be run right now, it would fail/throw some sort of error. Do we know when it was last run?

In any event, that URL seems at least temporarily invalid. My suggestion for this PR is to disregard those documentation builds for now and, subject to any corrections of this tab-link work, that the PR be merged into main.

[TG1999]

@johnmhoran some nits for your consideration

[TG1999]

@johnmhoran please add CHANGELOG for this and #1279

[johnmhoran]

@TG1999 In my current local CHANGELOG.rst, the most recent heading is Version v33.4.0. Should I add a bullet under that heading for issues #1286 and #1279? Or a new heading?

[TG1999]

@johnmhoran please add a new heading Next Release and put these bullet points under that

[johnmhoran]

Thanks @TG1999 -- will do.

[johnmhoran]

@TG1999 CHANGELOG.rst updated a little while ago.

[TG1999]

LGTM! Thanks++