Add "go to state" button in "try it out" mode about oppia HOT 7 CLOSED

I like this idea. Do you have any thoughts on what the UI should look like here 
so that it's not distracting and doesn't interfere with the flow?

Is it possible/feasible to have the actual exploration run inside a frame, then 
have the "go to current state" button (and maybe other controls in the future) 
outside of this frame, and have it open the state either in a new tab or in the 
same editing tab from which the exploration-testing tab originated

I want to throw in some ideas too.

An alternative UI would be to have exploration and state editor both opened 
side by side, and have state editor always follow the state changes in the 
exploration. If we can somehow highlite which rule was used to make the state 
transition, that'd be cool.
It would also be nice to be able to jump to any state (e.g. a drop down on the 
state editor side) and we jump into that state on the exploration side too.

And yet another alternative approach is to make state editor look as similar as 
possible to how the state would look in the exploration so we wouldn't need two 
views of the state (i.e. Versal approach).

Oh, that would be cool!
Jumping to any state is somewhat difficult because of parameters... The 
exploration has more "state" than just states. Gah. 

What I mean is jumping to a state in an exploration that has parameters should 
also involve setting those parameters manually to the values you want to test 
out (and hopefully these will be values that can actually occur naturally)

Currently, the exploration preview link takes the editor to exactly the same 
site as the one that would be displayed to an outside reader. We probably ought 
to have an actual exploration preview URL for the editor that also has "edit 
this state" functionality and other helpful links. (As a side effect, this will 
also fix issue 28.)

I don't think it is easy to jump to any state, for the reasons Yana mentioned 
-- at least not yet. In the future we can have some clever stuff going on in 
the backend that computes a viable set of parameters that a student reaching 
that state might have, but I think this will only happen in the distant future.

My main concern about having the state editor alongside the exploration is that 
it will probably take up quite a lot of space on the page. I do think, though, 
that it is a good idea to have the state editor look as similar as possible to 
the state that the reader encounters, and over time we ought to try and evolve 
the UI towards this. But this would probably still be a different UI from "try 
it out" mode, otherwise editors are probably going to get confused about when 
they are playing and when they are editing, if the full sets of both controls 
are available.

This should be fixed in 'develop' due to preview mode. Yana, could you please 
try this out and verify?

Marking as fixed.