Hide pipeline status in pipeline editor for new projects

What does this MR do?

For #325514 (closed)

When a user opens a new project and uses the pipeline editor to create a new CI configuration file, the pipeline status should be hidden since there are no triggered pipelines yet for the project. It will be visible once the user creates their first commit (and thus, triggers their first pipeline).

Screenshots

State	Screenshot
New Project (no CI file yet)
After committing

Recordings

Behavior for new projects New Project

Regression: Pipeline Status shows up for projects with a CI file With CI file

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 the pipeline status is still hidden behind a feature flag.
• [-] 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