Redirect users to the pipeline editor when clicking on CI/CD quick links

What does this MR do?

For #323694 (closed)

The quick links for CI/CD usually led to the single file editor. Now that we have the pipeline editor ready, we can start redirecting users to it by updating the links.

These are the links that have been updated:

• quick links on the project overview
• button on the jobs page (when there's no CI file)

Local Testing

Note when testing: the Set up CI/CD quick lins on the project overview is set to appear only when auto devops is not enabled. The condition in full is:

def cicd_missing?
  current_user && can_current_user_push_code? && repository.gitlab_ci_yml.blank? && !auto_devops_enabled?
end

You can test on the following cases:

• Project Overview
  • Blank project (no repository)
  • Project with no CI config
  • Project with CI config
• CI/CD > Jobs page (for projects with no pipelines or CI config yet)

Screenshots

Blank Project Blank Project

Project with no CI config Without CI Config

Project with CI config With CI Config

Jobs Page Jobs Page

Does this MR meet the acceptance criteria?

Conformity

• 📋 Does this MR need a changelog?
  • I have included a changelog entry.
  • I have not included a changelog entry because _____.
• [-] Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• [-] Style guides
• [-] Database guides
• [-] Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• [-] Tested in all supported browsers
• [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team