3a.UI Updates to include OSD flow 3b.to let the user know the prereqs for creating a connector

Problem: On the namespace page, the user has just one action button - Register eval namespace. Registering eval namespace stands out and unless a user reads the text, they wouldn't be aware of the 2nd flow we have - OSD add-on flow.

1.We should look into how can we give equal weightage to these 2 flows with the flexibility of allowing users to select from OSD, ROSA, ARO.. namespaces in the future.The UX team needs to explore what solution can make it clear to the user. 

2.The other problem we have is that a user starts the connector creation. Only during the connector creation, she realizes that she needs a provisioned RHOSAK instance and also requires the add-on to be installed on her org's OSD. She may drop from step 3 to go back and provision RHOSAk or install the add-on. 

UX team needs to explore how a user can be notified of the pre-reqs in advance. That way they can complete the prereqs and then start connector creation. This will reduce time for connector creation and also provides good user experience. 

Design thinking workshop comments:: https://miro.com/app/board/uXjVOxLMw0k=/?moveToWidget=3458764527503724309&cot=14