On install, conflicting components are created

[corinz]

When installing the crds, and operator via release.yaml with the instructions found here, the operator launches some Tekton components.

After step 1 is completed, the instructions advise the creation of a TektonConfig, which, after applied, deletes the original components, and replaces with them with new components (pods).

If the intent is to use release.yaml with a TektonConfig, the release.yaml should not create any components by default.

I propose that release.yaml only create the CRDs and operator, without installing any components by default.

Proposal: change AUTOINSTALL_COMPONENTS env var set in the tekton-operator/tekton-config-defaults configmap be set to false by default to prevent this collision/conflict.