Logging support for viewer app

[RFSH]

This PR,

• Adds proper log support to the viewer app (Logging in viewer app #1910). For the complete list of actions please refer to this google sheet.
• Add extra log info to distinguish between view button and the rest links (log eye v.s. link when direct to a record page #1917)
• Fix a bug in the viewer app which would cause users to be stuck in the edit form (Open edit form for an annotation, don't change anything and click on save.)
• Unhighlight annotations when switching to edit mode.
• Removed the unnecessary usage of slide_id in the code.
• Fixed a small bug in the logic of disabling the "show/hide annotation" button. It wasn't properly checking the value that osd viewer is returning.

[jrchudy]

The only thing I had a comment about was adding the logging functions to the annotation service. I think it makes sense to do it there but was wondering why in annotation service instead of the existing log service?

[RFSH]

@jrchudy I've done the same in table.js and faceting.js as well. I also did the same in recordedit in this PR (in recordCreate.js).

These functions are more specific to the ones in log service. They're mainly some wrappers that use the contextualized data in each place (for example in table.js it's using the logStack attached to vm or in annotation service I'm using the logStackNode that is attached to each annotation model) and call the general functions in log service. We could eventually move all these functions to log service and pass the contextualized data as well if we find a more general pattern in them.