Issue 130 and 118 resolution

[btruhand]

This PR introduces the following:

• A fix for issue 118. When users enter the ocean with a participant ID that is already being used (including by bots), they will receive a modal message that tells them the participant ID has already been used
• Experimenters can now click a hyperlink in their dashboard to see a participant's view during a simulation. The hyperlink is attached to the participant IDs shown in the 'currently active and tracked simulations' table. Each hyperlink will link the experimenter to the corresponding participant's view. The links are removed once a participant disconnects, either because an abrupt disconnection or the simulation has ended.
• The view that experimenters, or thus the observers, get from viewing the participants is an exact replica of the participant's view. However any buttons in the simulation cannot be clicked by the observers though they are still enabled purely for visual purposes. Also instead of 'You' to represent the viewed participant, an observer will instead see the name of the participant being viewed. Again for visual purposes.

[coveralls]

Coverage decreased (-0.77%) to 64.51% when pulling 11af9c3cbbd2977c50e7ad43bba82de643b1e19b on btruhand:issue-130 into 197d203bbef110c639c84210b89902909b9def24 on jorgearanda:master.

[jorgearanda]

This is a great patch, Btara! There are some things outstanding though--see if you can take care of them, else I will later on.

First, this is not quite a fix for #118 --it does prevent me from creating simultaneous participants with the same ID, but participant IDs can still be reused once the previous usage has ended. We should check the database to see if any participant has used this ID in this microworld in order to properly close the issue.

Second, there are cases--I haven't figured out exactly when, unfortunately--where the observer window is waiting on a "Loading the application" loop, and does not properly see what's going on until, I think, a new season starts.

And third, it would be great if the experimenter could access the simulations as an observer while the participant is still reading the instructions/getting ready. But it doesn't seem as if that's available at this point. Let me know if this is too cumbersome to add.

[btruhand]

Thanks for the comments Jorge!

At first point: Ah I thought participant IDs only need to be unique within a particular simulation, not for the whole microworlds.

At second point: Interesting, I thought I covered all the cases already. You can see the synchronizeObserverAndParticipantView in fish.js, that might help you find when observers are stuck in a loading the application loop.

At third point: You are right currently it's not possible to view a participant while they're still getting ready. I'd have to make some new UI for that. It'll be a bit of work to do.

Sadly I might not have the time to do anything on these for this week. But I'm fine to wrap this up in the following weeks. Let me here what you think

[btruhand]

Jorge, I've made it so that participants cannot use participant IDs that have already been used in the past and is used for bots. As an addition I've made it that bots' names have to be unique.

Right now the participant IDs that are used will remain in the microworld document even if the participant has finished/quit the simulation. I don't know if this is suppose to be the case, but if the participant IDs only need to be tracked as long as the participant is in the simulation then I can easily make it do so.

Unfortunately for the first issue that you raised I cannot find the problem and as I've mentioned in the email, I won't be able to resolve the third issue you raised.