Directory not handled in digest-to-results step

This will fix the issue of jib-maven task not passing digest to results
if the clone has happened in sub-directory and directory passed to
jib-maven task

It is because the directory param is not handled in path creation for digest

It will not break the existing the behaviour but fixing the issue for directory scenario
so doing the change in latest version

task/jib-maven/0.1/tests/run.yaml

@@ -48,7 +48,7 @@ spec:
     name: jib-maven-test-pipeline
   workspaces:
   - name: shared-workspace
-    persistentvolumeclaim:
+    persistentVolumeClaim:
       claimName: jib-maven-source-pvc
   resources:
   - name: build-image

task/jib-maven/0.2/tests/run.yaml

@@ -61,5 +61,5 @@ spec:
     name: jib-maven-test-pipeline
   workspaces:
   - name: shared-workspace
-    persistentvolumeclaim:
+    persistentVolumeClaim:
       claimName: jib-maven-source-pvc

task/jib-maven/0.3/tests/run.yaml

@@ -64,7 +64,7 @@ spec:
     name: jib-maven-test-pipeline
   workspaces:
   - name: shared-workspace
-    persistentvolumeclaim:
+    persistentVolumeClaim:
       claimName: jib-maven-source-pvc
   - name: ssl-certs
     configMap:

task/jib-maven/0.4/jib-maven.yaml

@@ -77,7 +77,7 @@ spec:
 
   - name: digest-to-results
     image: $(params.MAVEN_IMAGE)
-    script: cat $(workspaces.source.path)/target/jib-image.digest | tee /tekton/results/IMAGE_DIGEST
+    script: cat $(workspaces.source.path)/$(params.DIRECTORY)/target/jib-image.digest | tee /tekton/results/IMAGE_DIGEST
 
   volumes:
   - name: empty-dir-volume

task/jib-maven/0.4/tests/run.yaml

@@ -64,7 +64,7 @@ spec:
     name: jib-maven-test-pipeline
   workspaces:
   - name: shared-workspace
-    persistentvolumeclaim:
+    persistentVolumeClaim:
       claimName: jib-maven-source-pvc
   - name: ssl-certs
     configMap: