Add links from the Web client to the relevant documentation

[Jane Sandberg]

This idea was posted by Don Butterworth in this thread: https://markmail.org/message/m2yjmyodiy7uwdv3 -- see some discussion later on in that thread.

This would have to be configurable and customizable for two reasons:
1) Workflows, settings, and policies that are specific to a particular library, and which might be contradicted by the official documentation. A simple example would be one where the documentation provides step-by-step instructions to use Feature X when local policy is to never use Feature X. In those cases, it seems like the Library would want to turn off documentation links for that screen, or link to a specific piece of local documentation.

2) Documentation that is specific to a particular library/system/consortium. The example that jumps to mind is SITKA and their comprehensive documentation of Evergreen that is specific to their consortium.

[Remington Steed (rjs7)]

This sounds related to bug 1242717.