Improve design of /new project start-page for onboarding flow

[jldec]

The start page of the New Project onboarding flow contains some rough edges.

When app is not installed (GitHub only)

(see screenshot below)

• Replace Select a Git repository... with an explanation of what a Project is (under "New Project")

  Projects help you manage prebuilds and
  workspaces for your repository. Learn more

• Show a label above the dropdown:

  User or organization on github.com. (change)

• Show user account in the dropdown.
• Replace the box with "No Access..." with a friendlier explanation:

  Additional authorization is
  required for our GitHub App to
  watch your repositories and
  trigger prebuilds.
  Configure Gitpod App

• Remove Repository not found? line which is not relevant before the App has been installed.
• Remove Missing organizations? line which is too difficult to understand.
  (add to dropdown in separate issue)
• Remove or open a New Workspace with an example repository. note at the very bottom.

When repositories can be listed

(see screenshot below)

• Show the same explanation of what a Project is (under "New Project")

  Projects help you manage prebuilds and
  workspaces for your repository. Learn more

• Show (existing from before) instruction above the dropdown:

  Select a Git repository on xxx. (change)

• In the list, when a repo is "already taken", provide a hint for how to track down.
  See Mention the user who already imported the repository as a project #5119.

Additional

• Remove or open a New Workspace with an example repository. at the bottom. That was a just workaround for bypassing the option to choose from example repos on the website.

[jldec]

/schedule

Scheduling this now because it provides aditional context for #5583
Considering the scenario where a new repo is being created from a template, and the GitHub app is not yet installed, the first section above may be helpful, since it does not suggest selecting any repository from a list.
cc: @jankeromnes

[roboquat]

@jldec: Issue scheduled in the meta team (WIP: 0)

In response to this:

/schedule

Scheduling this now because it provides aditional context for #5583
Considering the scenario where a new repo is being created from a template, and the GitHub app is not yet installed, the first section above may be helpful, since it does not suggest selecting any repository from a list.
cc: @jankeromnes

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[laushinka]

Will pick this up. @gtsiolis we can align on the visual design?

[laushinka]

/assign

[laushinka]

@gtsiolis @jldec I'm assuming the tasks for when repositories can be listed depend on #5128? Other than that, do we still have pending discussions about what should happen here?

[laushinka]

Putting this comment in here for when we talk about the follow-up tasks to this issue #7163 (comment)

[jldec]

@laushinka I think we can close this issue - the changes from #7163 cover almost all of the points.
We can work through #5119 separately.

[laushinka]

@laushinka I think we can close this issue - the changes from #7163 cover almost all of the points. We can work through #5119 separately.

@jldec Oh you're right, I didn't realize. Awesome!

[jldec]

@gtsiolis feel free to open another issue to improve the UX/UI and design consistency of the repo list.