Annotation Tool: Bug Fix Filtered Personal Annotations on Page Load

**Background**: During the live testing of the tool, we found a bug which filtered the annotations from the table below the source, but not within the source itself during the "instructor tab". Basically if you set the default tab to be instructor, the tool would give you the instructor tool as well as your personal ones. 

**Studio Updates**: None.

**LMS Updates**:  When instructor is the default tab, you should only see instructor annotations instead of a mix of instructor and your own. 

**Testing**: Set up the text tool as usual (i.e. annotation storage url, secret token, advanced modules). Once it's set up add it to a module. In the settings for that component make sure you change the default tab to "Instructor" and that you add in an instructor email (helpful if it's valid, but also not necessary). Go into the LMS. Here create a few annotations (both as student and instructor, though if you didn't put a valid instructor email, you'll be looking for no annotations). Then reload the page. It should default to instructor with only the instructor annotations (if any) and none of your personal ones. Hitting the tab for "MyNotes" or "Public" should show you the appropriate annotations as well. Compare this to the current tool already in production which results in your personal annotations showing up alongside the instructor annotations. 

**Urgency**: It'd be helpful to have this in either the release candidate for the week of the 14th or the one in the 21st.  
It's not necessarily a hard and fast rule. But like English, whenspacesareomittedthetextcanbereallyhardtoread! Textbooks that don't break up text into chapters, sections and subsections (ie big line breaks) feel like endless mountains of text. Many of the same conventions you'd apply to writing a good essay - clear thoughts broken up into logical stanzas, good spelling, good explaining of your key concepts - apply to writing code. The easier your code is to read, the easier it is to review, maintain, and fix.

Given the number of bugs with Annotations in the past, coupled with the fact that very few edX'ers have a solid JS background, I think we really need readable and documented code, so I'm putting that at a premium.