Fix EE master failure: project_ci_cd_settings doesn't exist Job Failed

What does this MR do?

Something really weird happened https://gitlab.com/gitlab-org/gitlab-ee/-/jobs/168135367

What I think happened:

• The CE MR was properly reverted in CE: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/25566
• We waited for the auto merge to EE
• The auto merge to EE commit removed the migration but didn’t undo the schema version change: https://gitlab.com/gitlab-org/gitlab-ee/commit/da93e463713e426a4ae28c6c4c5f9f2dca4c0c2f

Fixing schema.rb seems to fix all the failures saying that project_ci_cd_settings table doesn't exist.

What are the relevant issue numbers?

Resolves https://gitlab.com/gitlab-org/gitlab-ee/issues/10036

Does this MR meet the acceptance criteria?

• Changelog entry added, if necessary
• Documentation created/updated via this MR
• Documentation reviewed by technical writer or follow-up review issue created
• Tests added for this feature/bug
• Tested in all supported browsers
• Conforms to the code review guidelines
• Conforms to the merge request performance guidelines
• Conforms to the style guides
• Conforms to the database guides
• Link to e2e tests MR added if this MR has Requires e2e tests label. See the Test Planning Process.
• EE specific content should be in the top level /ee folder
• For a paid feature, have we considered GitLab.com plans, how it works for groups, and is there a design for promoting it to users who aren't on the correct plan?
• Security reports checked/validated by reviewer

cc @lbennett