project_feature not created when creating self-monitoring project

Summary

After executing the 20190801072937_add_gitlab_instance_administration_project.rb migration, on attempting to open the GitLab Instance Administration project, the following error occurs (1 occurrence reported):

undefined method `access_level' for nil:NilClass
ProjectPolicy#feature_available?  app/policies/project_policy.rb, line 505
block (2 levels) in <class:ProjectPolicy>  app/policies/project_policy.rb, line 133
DeclarativePolicy::Condition#compute  lib/declarative_policy/condition.rb, line 23
block in DeclarativePolicy::ManifestCondition#pass?  lib/declarative_policy/condition.rb, line 44

This seems to occur because project.project_feature does not exist.

Workaround

Rerunning the migration using bin/rails db:migrate:redo VERSION=20190801072937 recreates the project with project.project_feature and stops the error.

Steps to reproduce

Unable to reproduce the error as yet. Attempts to force an error during creation of project.project_feature resulted in the migration failing (which is correct).

Example Project

(If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report)

(If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version)

What is the current bug behavior?

(What actually happens)

When visiting the GitLab Instance Administration project in a browser, this error occurs:

undefined method `access_level' for nil:NilClass
ProjectPolicy#feature_available?  app/policies/project_policy.rb, line 505
block (2 levels) in <class:ProjectPolicy>  app/policies/project_policy.rb, line 133
DeclarativePolicy::Condition#compute  lib/declarative_policy/condition.rb, line 23
block in DeclarativePolicy::ManifestCondition#pass?  lib/declarative_policy/condition.rb, line 44

What is the expected correct behavior?

(What you should see instead)

The project page should open, no error should occur.

Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.)

Output of checks

(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)

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

(If you can, link to the line of code that might be responsible for the problem)

cc @smcgivern @stanhu