Pre-compile HTML-stripping regexes.
move JS code into files and load using get_data instead of inlining the source
update jQuery to v2.0.2
update jQuery UI to v1.10.3
Merge remote-tracking branch 'kmicklas/js' into feature-kmicklas-js-files
Merge branch 'feature-flake' into develop-flake
Merge remote-tracking branch 'work/feature-kmicklas-js-files' into feature-ospalh-kmicklas-js

Conflicts:
	anki/js.py
Use qtips in the deck browser.
Re-do the cutting off of trailing “<br>”s.
Merge branch 'feature-ospalh-special' into feature-ospalh-kmicklas-js
Merge branch 'develop-ospalh-special' into feature-ospalh-kmicklas-js
don't die if autojunk unavailable (#952)
allow updates to existing notes in .apkg import
unbury in deckbrowser, not deckduelist() (#946)
rework sibling handling and change bury semantics

First, burying changes:

- unburying now happens on day rollover, or when manually unburying from
  overview screen

- burying is not performed when returning to deck list, or when closing
  collection, so burying now must mark cards as modified to ensure sync
  consistent

- because they're no longer temporary to a session, make sure we exclude them
  in filtered decks in -is:suspended

Sibling spacing changes:

- core behaviour now based on automatically burying related cards when we
  answer a card

- applies to reviews, optionally to new cards, and never to cards in the
  learning queue (partly because we can't suspend/bury cards in that queue at
  the moment)

- this means spacing works consistently in filtered decks now, works on
  reviews even when user is late to review, and provides better separation of
  new cards

- if burying new cards disabled, we just discard them from the current queue.
  an option to set due=ord*space+due would be nicer, but would require
  changing a lot of code and is more appropriate for a future major version
  change. discarding from queue suffers from the same issue as the new card
  cycling in that queue rebuilds may cause cards to be shown close together,
  so the default burying behaviour is preferable

- refer to them as 'related cards' rather than 'siblings'

These changes don't require any changes to the database format, so they
should hopefully coexist with older clients without issue.
Merge remote-tracking branch 'dae/master' into feature-flake

Conflicts:
	anki/collection.py
	anki/sched.py
	aqt/deckconf.py
Re-cleaned.
Merge branch 'feature-flake' into develop-flake
Merge remote-tracking branch 'ospalh/develop-flake' into feature-ospalh-kmicklas-js
Merge remote-tracking branch 'flake/develop-flake' into feature-ospalh-special