workloads with lifecycle:tekton templates go healthy==False

[tbr11]

Bug description:

Please provide a clear and concise description of what the bug is.

Steps to reproduce:

Please provide a set of steps to reproduce the behavior (example):

• Get a fresh cluster,
• Checkout catalog main
• Install TAP 1.7.0-build.35
• Install a basic supply chain
• Then:

k create ns foo

k label namespace foo apps.tanzu.vmware.com/tap-ns=""

tanzu apps workload create foo --git-branch main --git-repo https://github.com/vmware-tanzu/application-accelerator-samples --sub-path tanzu-java-web-app --label apps.tanzu.vmware.com/has-tests=true --label app.kubernetes.io/part-of=tanzu-java-web-app --type web -n foo -y --wait

This will fail with the following error:
Error: Failed to become ready: unable to retrieve outputs for resource [config-writer] in supply chain [source-to-url]: failed to find any healthy object in the set of immutable stamped object

A few minutes later the workload will show as healthy.

Expected behavior:

When a workload pairs with a template that is lifecycle:immutable/tekton

If the set of objects that has been stamped out contains at least one object that is in unknown state

Then the workload reports healthy==unknown.

Actual behavior:

When lifecycle:immutable/tekton

If the set of objects that has been stamped out does not contain at least one object that is in healthy state

Then the workload reports healthy==false.