Enable input to fuzz-introspector from fuzzer runs

[DavidKorczynski]

One other extension point we'd like to see is for infrastructure to be able to inject additional info into these reports.

e.g. on infra we have information about e.g:

• Where crashes are happening. e.g. if a fuzzer keeps hitting a particular crash that's blocking it from finding more interesting bugs.
• Other runtime blockers such as if something is allocating too much memory.

Originally posted by @oliverchang in https://github.com/ossf/fuzz-introspector/issues/226#issuecomment-1109130758

[DavidKorczynski]

@AdamKorcz in https://github.com/ossf/fuzz-introspector/pull/258 I add support for loading json files with information about bugs. Could you look into how to get this propagated into the calltree? For example, if we create an interface where we can simply attach one or more bugs to a given callsite index in the HTML code?

It would be nice if we have a few icons for each bug type (just use a placeholder for now) and then also when hovering a given thumbnail include the description about the bug or something?