Forks do not default to personal namespace

Summary

When forking a project, the expectation is that the user's personal namespace will be the default selection in the dropdown form. This is in line with both open source projects following a fork branching strategy as well as customers on GitLab enterprise who follow a forking model.

Steps to reproduce

  1. Select a project
  2. Click "fork"
  3. Under the fork form "project url", select that dropdown
  4. You'll see that the namespaces are in alphabetical order and do not default to your personal namespace

Example Project

What is the current bug behavior?

The project url dropdown is in alphabetical order, without defaulting to the user's personal namespace.

What is the expected correct behavior?

The user's personal namespace should be the first option and then the rest should be in alphabetical order.

Relevant logs and/or screenshots

Here's a recording from a conversation with this customer that was going through our change logs and seems to have found the exact commit where the fork form broke.

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info 

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


(we will only investigate if the tests are passing)

Possible fixes

9e2d32da That commit seemingly was when the logic changed. Release 14.9.0 in the CHANGELOG.MD.