Set identity during admin init (#181)

Follow-up of 
#177 

Motion container starts after other Singularity container starts hence
setting identity inside motion container does not take effect until the
user restart the docker compose.

To address above issue, we can set the identity to Motion during Admin
init script.

Tested end to end and see data reflected on Dashboard

https://dataprograms.grafana.net/d/f49ba403-a767-4243-af44-607dec1e7100/usage?orgId=1

fixes #174

.env.example

@@ -1,5 +1,5 @@
 # The version of singularity you will use to make deals. Generally, this should not change
-SINGULARITY_REF=:v0.5.4
+SINGULARITY_REF=:v0.5.5
 
 # Comma seperated list of storage providers motion should make storage deals with
 # You must set this value to contain at least one storage provider for motion to

docker-compose.yml

@@ -20,7 +20,7 @@ services:
 
   singularity_admin_init:
     image: ghcr.io/data-preservation-programs/singularity${SINGULARITY_REF}
-    command: admin init
+    command: admin init --identity Motion
     volumes:
       - motion-singularity-volume:/usr/src/app/storage
     environment:

integration/test/motionlarity/.env

@@ -1,4 +1,4 @@
-SINGULARITY_REF=:v0.5.4
+SINGULARITY_REF=:v0.5.5
 LOTUS_TEST='true'
 LOTUS_API=http://lotus:1234/rpc/v1
 MOTION_PRICE_PER_GIB_EPOCH=0