Make MultiRangeInlineEditor test that relies on editor interaction a true integration test...

... and wait for async functions to complete. For #5302.

Only the last test is affected by this (I just wrapped the other tests in a separate "describe" block so they would run with the normal unit tests). The other tests don't actually rely on the Editor functions that add the inline editor, so they can run in a mock editor in the Jasmine window. (It's worth reviewing the diffs with ?w=1 so you can see the actual changes more clearly.)

The last test actually calls the host editor to add the inline editor, and doesn't wait for async open/close of the inline editor to complete. In order for those to actually complete properly, the inline editor animation has to run, but that animation is defined in the normal Brackets CSS, which isn't loaded into the Jasmine window. So we open a test window to run the test in.

Note that even though there's only one test in that category right now, I open/close the test window in a `beforeFirst/afterLast` pair, so if more tests get added they can reuse the same window.