odo add binding asks all the questions even though a binding with the provided name already exists in the Devfile

[valaparthvi]

/kind bug

What versions of software are you using?

Operating System:
Fedora 35
Output of odo version:
v3.0.0

How did you run odo exactly?

1. Setup cluster with SBO, another operator and a microservice instance
2. Run odo add binding once.
3. Run it again and provide the same name as before.

Actual behavior

➜  odo add binding                                     
? Do you want to list services from: current namespace
? Select service instance you want to bind to: mongodb-instance (PerconaServerMongoDB.psmdb.percona.com)
? Enter the Binding's name: go-framework-mongodb-instance
? How do you want to bind the service? Bind As Environment Variables
? Select naming strategy for binding names: DEFAULT
 ✗  errors while adding components:
component go-framework-mongodb-instance already exists in devfile 

Expected behavior

➜  go-framework odo add binding                                     
? Do you want to list services from: current namespace
? Select service instance you want to bind to: mongodb-instance (PerconaServerMongoDB.psmdb.percona.com)
? Enter the Binding's name: go-framework-mongodb-instance
 ✗  component go-framework-mongodb-instance already exists, please enter a different name
? Enter the Binding's name: go-framework-mongodb-instance-2
? How do you want to bind the service? Bind As Environment Variables
? Select naming strategy for binding names: DEFAULT
 ✓  Successfully added the binding to the devfile.
Run `odo dev` to create it on the cluster.
You can automate this command by executing:
  odo add binding --service mongodb-instance.PerconaServerMongoDB.psmdb.percona.com --name go-framework-mongodb-instance-2 --bind-as-files=false

odo add binding should probably ask for the name first to ensure a binding doesn't already exist with the same name, or in case it does, it should not error out and ask the user to re-enter the name with a different value.

Any logs, error output, etc?

[github-actions]

A friendly reminder that this issue had no activity for 90 days. Stale issues will be closed after an additional 30 days of inactivity.

[github-actions]

This issue was closed because it has been inactive for 30 days since being marked as stale.