Add a check for Configuration History

Description of the test

As per !70025 (merged) / gitlab-org/quality/testcases#2276 (closed)

A fix is to be made to the codebase such that:

When a project does not have a .gitlab-ci.yml file

• The Configuration history link is not displayed
• the Enable Auto DevOps button is displayed

When a project does have a .gitlab-ci.yml file

• The Configuration history link is displayed
• the Enable Auto DevOps button is not displayed

This MR iterates over the existing Security Configuration end to end tests to provide these expectations

Check-list

• Confirm the test has a testcase: tag linking to an existing test case in the test case project.
• Note if the test is intended to run in specific scenarios. If a scenario is new, add a link to the MR that adds the new scenario.
• Follow the end-to-end tests style guide and best practices.
• Use the appropriate RSpec metadata tag(s).
• Ensure that a created resource is removed after test execution. A Group resource can be shared between multiple tests. Do not remove it unless it has a unique path. Note that we have a cleanup job that periodically removes groups under gitlab-qa-sandbox-group.
• Ensure that no transient bugs are hidden accidentally due to the usage of waits and reloads.
• Verify the tags to ensure it runs on the desired test environments.
• If this MR has a dependency on another MR, such as a GitLab QA MR, specify the order in which the MRs should be merged.
• (If applicable) Create a follow-up issue to document the special setup necessary to run the test: ISSUE_LINK
• If the test requires an admin's personal access token, ensure that the test passes on your local with and without the GITLAB_QA_ADMIN_ACCESS_TOKEN provided.