Content translation/Templates support rewrite 2016

We will use a whitelist approach for elements. Moving this kind of elements from source wiki to target with or without edits is generally difficult because of lack of template standardisation. That is a larger problem. But for CX, for a specific language pairs, instead of disabling and disallowing all of them, we can selectively enable some of them and live with that.

Keep all inline templates in source article. If the same template exist in target language wiki:
 * keep it as a readonly template.
 * Adapt template name using API, if no mapping exists.
 * Show a striped gradient as visual indication of readonly section.
 * Adapt template parameters if a mapping exists

If the same template does not exist in target wiki deconstruct the template and consider it as html content. Do not do machine translation for section marked non-editable - basically templates

By default we remove all block templates (templates resulting tables for example). For the first iteration of the project, our priority language pair is Spanish-Catalan. The top used templates in these wikis were analysed. In some cases, with the help of a template parameter mapping we can adapat the template for the target langauge. Template editing will not be possible, it will be just copy from eswiki with template name translated.

The whitelisting is driven by a configuration file per language pair. It is a json file and a sample entry for the above mentioned case for es-ca is given below