Augment odo link to allow linking operator and a component

[girishramnani]

[kind/Feature]

Which functionality do you think we should add?

Once we have a running operator, odo should have the functionality to link that operator backed service to a component.
We are going achieve that using Service Binding Operator https://github.com/redhat-developer/service-binding-operator.
After a discussion with the team building service binding operator, we realised that this can be done without the use of an operator.

• we will augment the already present odo link operator to link the operator with a component.
• odo link will work as expected with for non operators pieces ( components and service-catalog services )

[girishramnani]

after a discussion with service binding operator team, we can go without that and use internal constructs

[girishramnani]

but as someone went to the trouble of building an operator for service binding, there would be some self healing features which we won't be able to implement.
This is because operators are reactive in nature but when we add linking feature in odo link it cannot react to events occuring on the cluster. But the tradeoff shouldn't be that huge as odo is intended for development mode.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[girishramnani]

This issue is duplicate of many issues broken down with more information hence closing