Change instruction text to be more inclusive of those with accessibility requirements

What does this MR do?

Change the text of an instruction from "Click" to "Select" to be more appropriate for users who only use a keyboard.

Are there points in the code the reviewer needs to double check?

I'm not sure if 'account' is the most appropriate term in 'Select an account...'. The code uses the term namespace, but that doesn't seem appropriate to present to users. Would 'profile' be better, or 'username'?

There may be other places in the code where similar language could be improved. Would it be worthwhile me doing a review and adding them to this MR?

Why was this MR needed?

To be more inline with accessibility guidelines.

Does this MR meet the acceptance criteria?

• Changelog entry added, if necessary
• [ ] Documentation created/updated
• [ ] API support added
• [ ] Tests added for this feature/bug
• Review
  • Has been reviewed by UX
  • [ ] Has been reviewed by Frontend
  • [ ] Has been reviewed by Backend
  • [ ] Has been reviewed by Database
• [ ] Conform by the merge request performance guides
• Conform by the style guides
• Squashed related commits together
• Internationalization required/considered
• [ ] End-to-end tests pass (package-and-qa manual pipeline job)