Use a normal .trim() on the sockmaster name

This should prevent us ending up with pages like [[Wikipedia:Sockpuppet investigations/ Justme78783]]
Merge pull request #174 from legoktm/patch-1

Use a normal .trim() on the sockmaster name
Replace another trimRight with trim
fluff: more intelligent edit summary handling

The user contributions link could sometimes push the edit summary over
the limit of 255 characters, causing it to be truncated. And the
"restore this version" feature didn't have the link at all.
This commit fixes these problems, per request at WT:TW.
Add {{news release}} to templates available, per #178

This does not fully implement the template; per the template
documentation, {{news release}} should be added to the article's
*talk page* for articles requiring *minor* cleanup
Add timestamp parameter to G13 (fixes #175)

Add getCurrentID() to the API of Morebits.wiki.page

Minor style changes for consistency, expand jshint.json

Passing the pageobj seems overkill though (as we're using it only
for G13), but I don't see a better solution
morebits: make use of new wgIsRedirect variable

This approach works on edit/history pages, so is better than dumbly looking for the redirectText CSS class.
We still can't do better for soft redirects, though, since MW has no built-in support for them.
fluff: automatically accept rollbacks when carried out by a reviewer or sysop

When you undo a single edit via index.php, the undo is automatically
detected as returning the page to a stable revision, and is therefore
automatically accepted. But this is not true of the API.
Per request on WT:TW, and pending the resolution of MediaWiki bug 54812.
Merge branch 'master' of https://github.com/azatoth/twinkle.git
fluff, speedy: remove bogus "_tab" target

"_blank" will open the content in a new tab if the browser is configured
appropriately (which it almost always is nowadays). "_tab" is just
another window name.
tag: add "notify page creator" option for {{not English}}

Per request at WT:TW.
tag: make patrolling the page optional

I was going to remove the "group" checkbox, to save space, but I don't
think that is necessary.
morebits, config: new namespaces

Education Program is not really relevant to Twinkle (editing is restricted), so leaving it out of config.
config: update to new TOC object model
morebits: misc. amendments to QuickForm

- The custom event on radios and checkboxes now fires after the
  subgroup is created, meaning that the custom event has access to the
  subgroup's controls
- And yes, the subgroup does need to be cloned!

These are in relation to an upcoming overhaul of twinklespeedy.
morebits: fix the amendments to QuickForm

Sorry about this. This bit of code is really quite subtle, and I missed
the point in the last commit. But I think I've finally fixed it once and
for all. Let's hope!
speedy: convert to use subgroups, other misc. changes

In hindsight, this should have been done in several "atomic" commits, but
so much for that idea!

Changes include:
- removing calls to prompt() when CSD-tagging an article and replacing them
  with subgroups, similarly to the tag module in 7acac36968087168ab6c4eb5b823381b6887b8ae
  (based on feedback on WT:TW and inspired by Siddhartha Ghai's work)
- overhauling the means by which the list of criteria is prepared. This
  makes it more flexible, to suit the variety of "modes" in which it can
  exist (e.g. checkboxes/radio buttons), and also future-proofs it against
  future changes
- changing the getParameters function to validate the subgroup inputs
  instead of displaying prompt dialogs
- various updates to the logic of the parameter inputs (e.g. several that
  were optional are now mandatory, to match the behavior of the associated
  db- template)
- removal of speedyPromptOnG7 pref - now unnecessary
- simplification of G13 API query added in 34fa87340b9e4ae37927d38be7e4d201ee94ac3a

It has been tested in various scenarios. Fingers crossed that it works in
*every* scenario!
Reduce pages where prefs notification box shows (per #183)
morebits: add primitive AbuseFilter handling

This only handles the "warn" and "disallow" AbuseFilter actions. It
really needs improvement per the comment on line 2362.
Per issue #182.
protect: add support for the new templateeditor protection level

It's only available in the Template and Module namespaces, which is an
artificial restriction, but helps to reduce clutter in other namespaces
where it is really irrelevant.