Select DOM elements with wildcard syntax

- DOM lookups were being done with non-existent literal selectors, so it
  was returning empty lists. As assertions were to be made while
  iterating over the list of elements, nothing was actually being
  verified.

- Common code has been centralized in the setup function. By declaring
  CSS selectors once, we minimize the odds of inadvertently using the
  wrong selector, as happened here.

- Had these tests actually been iterating over a non-empty list, this
  would have thrown undefined exceptions. jQuery.each calls its handler
  with an index and an item/object as the arguments. However, the object
  is a DOM-object, not a jQuery-object.  These tests break, as they had
  assumed the latter.

This test currently fails, meaning that the existing tests weren't
testing what they claimed.

Assertions are made for each element returned by the CSS selectors.
However, the selectors are assumed to be wildcard matches, but are
actually literal selectors. As there are no matched elements, this
causes the assertions to be (silently) checked zero times, without
failure.

Transition to Oqaque Keys

Update translations (autogenerated message)

ORA2 release-2014-06-13T11.52

Fix incorrect video bok choy test.

Squashing commits

Transition to Oqaque Keys

Bug fixes

Fixing regenerate_user

Ignore *.css.map files

Fix failing test and update documentation of video player

Sarina/fix underscore resource

Fixes BLD-1115

Fix wiki search query

Update SASS ( 3.3.5), Bourbon ( 4.0.2), Neat (1.6.0)

see http://blog.sass-lang.com/posts/184094-sass-33-is-released for more information on 3.3+ variable scoping

Note: this requires SASS 3.3+ so do ```bundle install```

3 entries for June -> 1 entry

and formatting error in a doc file.

Hotfix 2014-06-11

Do not merge zh-hk into zh-tw in darklang

Remove unused .reviewboardrc

clarify and internationalize the search spell correction message.

Allow users that have unregistered from a verified course to re-register.