Refactor TektonComponent with new refactoring changes

[sm43]

With recent refactoring of Operator, we have disabled TektonComponent as we have changed the status
for components and condtion used in status for them.

We can refactor the TektonComponent with the common things which are there in all components now and so that
there will be uniformity between all components method.

Refactoring PRs #385, #408, #421

Update the status methods which are common in status

operator/pkg/apis/operator/v1alpha1/common.go

Line 49 in 0390095

type TektonComponentStatus interface {

Once dashboard and results start using TektonInstallerSet we can update them otherwise they will break as they still use TektonComponent.

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[nikhil-thomas]

/remove-lifecycle stale

[nikhil-thomas]

@sm43 if you think all the reconcilers are ready to accept TektonComponent refactoring, then could you add a help-wanted label to this issue.

[sm43]

@sm43 if you think all the reconcilers are ready to accept TektonComponent refactoring, then could you add a help-wanted label to this issue.

once #548 is done, we would be able to do that. Results still uses older installation approach.

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.