[#19] Run mock api in different port in tests
[#14] Add action to get latest pending task

This will allow us to check if a dataset is pending creation or has a
pending update, and validate against duplicated names.

Only sysadmins can access this action, as the task contains the pending
data_dict. Also restricted access to task_status_show
[#14] Add validator to check pending dataset names

This is to avoid creating two datasets with the same name while creation
requests are being processed.
[#14] Modify package_create behaviour and add auth tests

We want all dataset creations to be forwarded to the EC API, so we
override the default `package_create` forwarding requests to
`dataset_request_create`.

To still have the ability to create datasets locally (and not request
their creation to EC), an `local_action` option has been added to the
context. Only sysadmins will be able to do it. This will be useful eg to
create harvest sources.

Auth tests has been added but settings like whether users need to belong
to organizations to create a dataset or allowing unowned datasets need
to be discussed.
Move run_mock_ec to tests root so it can be reused
[#14] Expire TaskStatus on `dataset_request_create`

Otherwise when requesting `pending_task_for_dataset` later on you didn't
get the latest version.

Fixed action tests to take this into account.
[#14] Add custom landing page for pending datasets

If a dataset has been submitted for creation to the EC API, the dataset
page will show a temporary page until the request has been completed. It
will probably ping the server periodically to check the status and
refresh when ready. This is left for the next iteration.

On most cases dataset creation should take seconds so perhaps we can
bypass this page entirely.
Merge branch 'master' of github.com:okfn/ckanext-glasgow