Output service name when creating Operator backed service

[dharmit]

What type of PR is this?
/kind bug

What does this PR do / why we need it:
It fixes a bug which leads to bad UX.

Which issue(s) this PR fixes:

Fixes #4013

PR acceptance criteria:

• Unit test

• Integration test

• Documentation

• I have read the test guidelines

How to test changes / Special notes to the reviewer:
Create an Operator backed service without providing a name. You should now see the service name being used from the alm example:

$ odo service create etcdoperator.v0.9.4-clusterwide/EtcdCluster
Deploying service of type: EtcdCluster
 ✓  Deploying service [3ms]
 ✓  Service 'example' was created

Progress of the provisioning will not be reported and might take a long time
You can see the current status by executing 'odo service list'
Optionally, link etcdoperator.v0.9.4-clusterwide to your component by running: 'odo link <component-name>'

Earlier, we were seeing Service ' ' was created.

[dharmit]

Failures seem unrelated to the PR:

 • Failure [244.365 seconds]
odo sub component command tests
/go/src/github.com/openshift/odo/tests/integration/cmd_cmp_sub_test.go:13
  Creating component using symlink
  /go/src/github.com/openshift/odo/tests/integration/component.go:694
    Should be able to deploy a spring boot uberjar file using symlinks in all odo commands [It]
    /go/src/github.com/openshift/odo/tests/integration/component.go:712
    No future change is possible.  Bailing out early after 240.941s.
      
    Running odo with args [odo component push --context /tmp/jhlemvwiph]
    Expected
        <int>: 1
    to match exit code:
        <int>: 0
    /go/src/github.com/openshift/odo/tests/helper/helper_run.go:34
------------------------------
• Failure [242.904 seconds]
odo sub component command tests
/go/src/github.com/openshift/odo/tests/integration/cmd_cmp_sub_test.go:13
  when component is in the current directory and --project flag is used
  /go/src/github.com/openshift/odo/tests/integration/component.go:493
    creates a local python component, pushes it and then deletes it using --all flag [It]
    /go/src/github.com/openshift/odo/tests/integration/component.go:521
    No future change is possible.  Bailing out early after 240.726s.
      
    Running odo with args [odo component push --context /tmp/573221927]
    Expected
        <int>: 1
    to match exit code:
        <int>: 0
    /go/src/github.com/openshift/odo/tests/helper/helper_run.go:34 

/retest

[mik-dass]

Can we add a check here https://github.com/openshift/odo/blob/e6be2586f5824bade91599f24686def26b53f1ee/tests/integration/operatorhub/cmd_service_test.go#L80
to verify that output contains the required name?

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dharmit

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• pkg/odo/cli/service/OWNERS [dharmit]
• tests/OWNERS [dharmit]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[dharmit]

Can we add a check here

https://github.com/openshift/odo/blob/e6be2586f5824bade91599f24686def26b53f1ee/tests/integration/operatorhub/cmd_service_test.go#L80

to verify that output contains the required name?

Makes sense. Added.

[mik-dass]

/lgtm