Add possibility to inject custom behaviour into TracePage [Subtask]

[aocenas]

Requirement - what kind of business use case are you trying to solve?

Subtask from #507

Problem - what in Jaeger blocks you from solving the requirement?

Proposal - what do you suggest to solve the problem or improve the existing situation?

For Grafana, there is a requirement to provide custom behaviour and in the future maybe even a custom elements. This encompasses things like custom navigation on clicking on span tags or showing additional context information in a modal. This can be done by injecting those to the extracted components as props or with provider pattern.

(@everett980) We have some patterns for customizable behavior (so far custom linking/annotating and optional scripts), but this will definitely require some bolstering to have optional click handlers and UI elements.
We have plans to make the config a JavaScript file instead of a JSON file, which would be a different way of defining these handlers/UI elements but would probably be consumed the same way as optional props from a parent component.

As mentioned this overlaps a bit with existing configuration though there probably isn’t need to make those 1 to 1 as I assume importing the trace components will and should allow for more fine grained control than is needed from standard Jaeger configuration.

Any open questions to address

[jkowall]

Grafana decided to do their own fork to reskin, so I am closing this out.