Releeph: use relative URIs

Summary: I used the `PhabricatorEnv::getProductionURI()` in too many places to build Releeph URIs.  The only places that should need full URIs are the links generated for Releeph emails, and in Conduit responses that link to Releeph objects.

Test Plan:
- Grep for `getProductionURI()` in Releeph, and make sure only sensible, non-DOM building places use it.
- Inspect the Releeph DOM to make sure hrefs etc. are relative.

Reviewers: wez, epriestley

Reviewed By: epriestley

CC: aran, Korvin

Differential Revision: https://secure.phabricator.com/D5999

src/applications/releeph/editor/ReleephRequestTransactionalEditor.php

@@ -265,7 +265,7 @@ final class ReleephRequestTransactionalEditor
     $body->addTextSection(
       pht('RELEEPH BRANCH'),
       $project_and_branch."\n".
-      $releeph_branch->getURI());
+      PhabricatorEnv::getProductionURI($releeph_branch->getURI()));
 
     return $body;
   }

src/applications/releeph/storage/ReleephBranch.php

@@ -98,7 +98,7 @@ final class ReleephBranch extends ReleephDAO {
       rawurlencode($this->getBasename()),
       $path
     );
-    return PhabricatorEnv::getProductionURI(implode('/', $components));
+    return implode('/', $components);
   }
 
   public function loadReleephProject() {

src/applications/releeph/storage/ReleephProject.php

@@ -51,7 +51,7 @@ final class ReleephProject extends ReleephDAO
       $this->getID(),
       $path
     );
-    return PhabricatorEnv::getProductionURI(implode('/', $components));
+    return implode('/', $components);
   }
 
   public function setDetail($key, $value) {