Remove ci_pipeline_latest feature flag

This feature flag was introduced in 13.2 and is now ready for removal

Changelog: other

app/models/ci/pipeline.rb

@@ -610,8 +610,6 @@ module Ci
     # rubocop: enable CodeReuse/ServiceClass
 
     def lazy_ref_commit
-      return unless ::Gitlab::Ci::Features.pipeline_latest?
-
       BatchLoader.for(ref).batch do |refs, loader|
         next unless project.repository_exists?
 
@@ -623,11 +621,6 @@ module Ci
 
     def latest?
       return false unless git_ref && commit.present?
-
-      unless ::Gitlab::Ci::Features.pipeline_latest?
-        return project.commit(git_ref) == commit
-      end
-
       return false if lazy_ref_commit.nil?
 
       lazy_ref_commit.id == commit.id

config/feature_flags/development/ci_pipeline_latest.yml

----
-name: ci_pipeline_latest
-introduced_by_url: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/34160
-rollout_issue_url: 
-milestone: '13.2'
-type: development
-group: group::pipeline execution
-default_enabled: true

lib/gitlab/ci/features.rb

@@ -10,10 +10,6 @@ module Gitlab
         ::Feature.enabled?(:ci_artifacts_exclude, default_enabled: true)
       end
 
-      def self.pipeline_latest?
-        ::Feature.enabled?(:ci_pipeline_latest, default_enabled: true)
-      end
-
       # NOTE: The feature flag `disallow_to_create_merge_request_pipelines_in_target_project`
       # is a safe switch to disable the feature for a particular project when something went wrong,
       # therefore it's not supposed to be enabled by default.