Rah export

[danielfdsilva]

Adds the api endpoint to export project results to the RAH repository.

Todo:

• Add unique instance id to avoid conflicts if multiple instances publish to the same RAH repo.

To consider:

• At this moment if a user tries to export results for a project which still has to be merged the export will be rejected. This prevents multiple exports with the exact same data from being created but rises a potential problem. If when the PR is merged and the branch is not deleted it will prevent the project from being exported again since this check depends on the branch existence. Thoughts @olafveerman ?

[danielfdsilva]

@olafveerman To solve the "to consider" situation we could add to the guide that the branch must be deleted after the PR is merged.

[olafveerman]

This looks great @danielfdsilva.

Things we should do before merging:

• handle the failing test
• add some documentation in the Readme about the feature. What it does, pointing to the RAH repo.

We should also document this in the RAM deployment repo: https://github.com/developmentseed/ram-deployment/blob/master/.kes/config.yml

[danielfdsilva]

@olafveerman Test fixed, and documentation added.

As for the ram-deployment repo, should we include the variables to integrate with RAH? Anything else?