Try to split into three separate components -> controller, tester,
and 'tasks' (postgresql-tasks in our case).  The controller
component is the main part which is able to run the task remotely.
Tester is more-like library for 'tasks' component (should be
reusable on the raw git level).

* controller: Almost separated component.
* postgresql-tasks: Likewise.
* tester: Likewise.

Allow automatized generating of data structures on remote host.
Run like ./remote_generate IP_ADDRESS.

* gen-data/dist/dist: New file.  Wrapper around tar to package
important files for data generation.
* gen-data/dist/dist.list: Include list for ^.
* gen-data/dist/dist.exclude: Exclude list for ^.
* gen-data/prep: Remote script to prepare everything for
successful ./generate run.
* gen-data/remote_generate: Wrapper running all the above.

In F20+ we should be able to deal with upgrades where user (or
system itself) changed the system locale like from 'en_US.utf8' to
'en_US.UTF-8' (which is just a syntax change).  Data generated by
this task should help testing this.

* gen-data/tasks/templates/locale-change.sh: Add new template for
locale related data-generation.
* gen-data/tasks/locale-cz/run.sh: Reuse template ^^.
* gen-data/tasks/locale-utf-typo/run.sh: New file for
'en_US.UTF-8' to 'en_US.utf8' switch. Reuse template ^^.

This data should help with checking of 'postgresql --upgrade'
behavior when the system locale changed significantly (from
en_US.UTF-8 to cs_CZ.utf8).

* gen-data/tasks/locale-cz/run.sh: New task file.
* gen-data/generate (locale_prereq): Fix missing LANG= prefix in
expected locale.  Quote current/expected locale strings in error
output.
(single_task): Adjust $INDENT in sub-shell to not affect
subsequent calls.  Create tarball in $OUTPUTDIR rather than in
`pwd`.  Introduce hook_end callback.
(generate_tasks): Use dynamic list of tasks.

Add also first task 'basic' which generates simple 'pagila'
database.

* generate: New file.
* databases/pagila.sh: New database file.
* tasks/basic/run.sh: New task file.