Added --namespace option to set the namespace of repacked tables

Bumped version number to enforce extension re-creation as the SQL has
been modified.

Current limitations:

- Check for namespace existence: on error temp objects are left around
- What happens to the indexes?
- Tests needed.
- Should the default be the GUC default_tablespace instead of pg_default?
  This is actually an original pg_repack shortcoming, not a regression.
Added --moveidx command line option

The option is only parsed, not implemented yet.
Added tests for the namespace change feature

Currently not passing as --moveidx not implemented yet.
Merge branch 'master' into change-tablespace
Added check for target tablespace existence
Added implementation for --moveidx

Note: if original namespace is "foo bar", repack_indexdef gives a bad
result. This is weird as apparently skip_ident can deal with spaces in
a quoted identifier. Committing as I'm going home, will deal with that
later.
Fixed index definition tokenization

In the previous commit skip_const was going ahead the space thus removing the
starting quote. Also fixed (and tested) trailing part after the tablespace
name, e.g. the WHERE clause.
Added documentation for --tablespace and --moveidx
Added missing entries to the pg_repack 1.2 changes
More helpful error messages in case of conflicting triggers

Closes issue #5.
Imply --no-order for non-clustered tables

--no-order can still be specified to VACUUM FULL a clustered tables
(not so useful I guess...)

Fixes issue #6.
Options sorted in a slightly more rational order

--no-order now is almost useless, but list it next to --order-by.
--jobs only specifies how to do something, not what to do. On the
same basis probably --no-analyze should be pushed further up.
Merge branch 'change-tablespace'

Conflicts:
	bin/pg_repack.c
	doc/pg_repack.rst
Had to shorten the tablespace metavar

In the rst docs two spaces are required between option and doc.
More explicit error message if the version functions are not found
Dropped redundant check for missing schema

If the schema is missing we have already stopped trying to check
the version numbers above.
Dropped unneeded error check

if pgut_execute fails it bails out.
Using elog instead of printf to report what database we are on

I know the ... is pretty but it messes up with warnings etc. By the way there
was a \n so the skipped part wasn't even going on the same line.
Logging the table we are working on at info level
Merge branch 'logging-cleanup'