Wrong header when creating new security policy

Summary

When user creates new security policy

Wrong header is rendered in policy editor:

Instead of new policy it says edit policy

Description	UI
merge request policy
scan execution policy

Steps to reproduce

1. Go to Project/Group
2. Secure -> Policies
3. New policy -> merge request/execution policy
4. Check header on top of policy editor

Example Project

What is the current bug behavior?

Wrong Edit header is rendered, when new policy is created

What is the expected correct behavior?

Header should reflect if we create New policy or edit existing one

Relevant logs and/or screenshots

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