Tune postgres memory usage based on available mem

On standalone gears, use maximum available memory to set parameters.
Tune MySQL parameters via OPENSHIFT_GEAR_MEMORY_MB
Ensure Drupal gears can migrate

This is a redo of f9c1089, which addressed
https://bugzilla.redhat.com/show_bug.cgi?id=1008043 and
https://bugzilla.redhat.com/show_bug.cgi?id=1013673.
Guard against removing innoDB logs
Bug 1019132 - removed member is not saved
Process postgresql.conf on each cartridge startup

Basically mimicing what MySQL cartridge does.
Difference in ERB template location is taken into account.
Fix bug 987758 - formtastic error rendering
Bump up memory for standalone cartridges
Bump MyISAM memory parameters

Based loosely on
http://serverfault.com/questions/354872/best-my-cnf-configuration-for-a-8gb-mysql-server-with-myisam-use-only
Fixing origin extended tests
Fix extended tests
typo fix
Allow gear_size parameter during application creation and cartridge addition.
Double up memory limits for embedded MySQL cart
Add description field to endpoints so that TLS urls can report what they are for.
Use oo-erb instead of erb
oo-diagnostics: Fix check for mlocate package

test_altered_package_owned_configs: Check the exit code of `rpm -q mlocate`
instead of checking the output.

The old code erroneously assumed that the rpm command would give no output
if the package were not installed, and so it would always return true even
if mlocate were not present.
oo-diagnostics: openshift-iptables-port-proxy

test_services_enabled: Check for openshift-iptables-port-proxy instead
of openshift-port-proxy (the former supersedes the latter).
<suggestions> record type as attr too

Eventually we will need to serialize suggestions and provide them via an
API. Using to_json the class of the suggestion is not saved, so record
it as an attribute too.
<oo-admin-chk> test for node hostname changes

Adds a report for the following situation:
a) User adds a gear to a node
b) Admin changes the hostname of the node, making the app essentially
inaccessible by the user via broker and causing loads of other problems.

While looking through all gears the nodes report, this now checks that
the node hostname matches what is in the DB for the gear. This could
briefly give spurious failures if a gear is being moved at the time, but
should otherwise be considered a legitimate problem.