Implement a Tekton Pipeline with a finally task, workspace sharing between tasks, and a TaskRun result consumption pattern for a build-test-deploy flow

Steps

1. Define a Pipeline with tasks and a finally block, using workspaces at the Pipeline level and binding them to task workspaces so build artifacts produced by earlier tasks are available to later ones
2. Configure a clone task that fetches the source repository into the shared workspace, followed by a build task that reads the source and writes the image digest as a task result
3. Reference the build task's result in the deploy task using the $(tasks.build-task.results.image-digest) syntax to pass the built image reference to the deployment step
4. Add a finally task for cleanup or notification that always runs regardless of pipeline success or failure, and use the $(tasks.build-task.status) variable to conditionally set its behavior
5. Create a PipelineRun with workspace bindings mapping the shared workspace to a PersistentVolumeClaim and observe the task execution order and result propagation in the Tekton dashboard or CLI