Fix: WYSIWYG now returns valid HTML in tables

The WYSIWYG by default creates invalid HTML5. Creating a table and running it through W3C validator returns the following error: The border attribute on the table element is obsolete. Use CSS instead.
Update modeladmin.md

Corrected many broken link-renderings. Also removed the "Related" link to [genericviews Module](http://silverstripe.org/generic-views-module) because it doesn't work, and I can't it elswhere.
Update i18n.md

Fix a link being inside backticks, which broke the formatting.
Update datamodel.md

Fix broken link to SS_List->column
Update i18n.php

Norwegian should use 'nb' and not 'no' in common languages array
BUG using isDev or isTest query string no longer triggers basic auth
BUG: Fix incorrect common_languages config
Updated HtmlEditorField Field()

I had a need to use onBeforeRender on a DataExtension of
HtmlEditorField and noticed it wasn't there. Added return
parent::Field($properties) use FormField::Field which utilizes
onBeforeRender.
Update templates.md

Changed Fragment links to Anchor links, however it's is slighty confusing what the right name for the thing is.
According to w3.org: "Some URIs refer to a location within a resource. This kind of URI ends with "#" followed by an anchor identifier (called the fragment identifier)." - http://www.w3.org/TR/html401/intro/intro.html#fragment-uri

After doing some research in the most common used name for the #some-link identifier I came to the conclusion that most of the time (about 70% on StackOverflow/BlogArticles/Interwebz) Anchor-link was the term used to describe the identifier. Imho, Anchor is the prefered term for the identifier.

Is it acceptable to change fragment to anchor, since it seems more used?
FEATURE allow force resampling on images
Fixed wrong variable name in modeladmin docs
API Debug::dump in CLI no longer generates HTML. Uses colours.
API Column size is configurable in DebugView
Upgrading TinyMCE dependency from 3.5.8 to 3.5.11
Better encoding of javascript
Fixes #2988
BUG Config::merge_array_low_into_high() ignores falsey values

Specific case: LeftAndMain::$session_keepalive_ping = true cannot be
set to false in config.yml for some cases because the value is ignored
when merge_array_low_into_high() is processing the config arrays.
Revert "BUG Config::merge_array_low_into_high() ignores falsey values"
Fatal errors should always return false

This allows PHP to set the exit code on fatals.
Updating the WAMP docs to include composer installation and apache 2.4 fix - delete index.php

Now uses GFM for code blocks.
BUG #3282: Added ability to subselect with in left or inner join
BUG Fix several issues around onmatch/onunmatch entwines.

1. Add missing _super calls.

2. Make UI widget destroys more consistent to avoid exceptions.
Selectable would throw an exception in the GridField.js if destroy
called from onunmatch - at that stage jQuery UI would have had called
the destroy already. Add a guard, and change to onremove, which triggers
before the element is removed from DOM.

3. DOM traversal fails after the element is removed from DOM.
Onunmatch triggers after the removal of the element from the DOM, which
makes DOM traversal fail. Use onremove instead, which triggers while the
element is still in DOM.