This only happens in some places, not on page loads.  But it breaks
javascript in weird ways as browser tries to render extra thigns.  This
manifested as breaking visual editor.

Change is based on https://www.mediawiki.org/wiki/Manual:$wgUser

(See https://chat.opentechstrategies.com/#narrow/stream/\
45-Lever-for.20Change/topic/API/near/97885 for context.)

Mainly the addition of LFC Admins and LFC Pseudo Decision Makers.

A part of the ansible refactor, the permissions for users needs to be
more fleshed out.  This adds specific groups for the api partners.

1) enable for sysops, and 2) hide the mediawiki [Edit] section links
when the proposal has edit enabled.

With the ansible configuration centralized into a top level torque-sites
directory (roles), the majority of the tasks main.yml and supporting
files can be removed with the roles being added to the top level
playbook.

This required a change to the base roles:

* Add rss as a base role for the RSS extension
* Add api roles to ase permissions
* Fill out some roles (like psuedo board member)
* Add board members to okta groups we knwo about
* Add login override
* Respect local login flag when rebuilding the login page

With the ansible configuration centralized into a top level torque-sites
directory (roles), the majority of the tasks main.yml and supporting
files can be removed with the roles being added to the top level
playbook.

This required a change to the base roles:
* Board Members from Okta are Decision Makers

With the ansible configuration centralized into a top level torque-sites
directory (roles), the majority of the tasks main.yml and supporting
files can be removed with the roles being added to the top level
playbook.

This required a few changes to the base pipeline:
* Add composer to mediawiki install
* Composer version update
* Add postgres base package
* Add LFC Evaluators as a known SAML group
* Add pre-req installation for mediawiki

Then removing all the old stuff from 100Change2017 and updating
the yml file to reference the general stuff.

Clean it up so things are a bit more declarative, as well as moving the
simpelsaml group config code over to the permissions, so that the
separation of concerns is a bit more straightforward.

Issue #62: Create security model for torque-sites
Issue #64: Pluralize the names of the abstract user groups

A lot of the configuration was inline blocks that were dumped directly
into LocalSettings.php.  This change separates those configurations out
into their own files for easier maintenance and documentation.

Issue #59: Change MediaWiki configurations to have multiple files