Include coverage reports from child pipeline

What does this MR do and why?

Include coverage reports from child pipelines when creating pipeline coverage report.

Part of #363301 (closed).

Screenshots or screen recordings

In this sample MR, alberts-gitlab/test-ruby-cobertura!2, there is a parent and child pipeline set up to generate coverage. The parent pipeline generates coverage for demo.rb. The child pipeline generates coverage for demo_child.rb.

Before - coverage from child pipeline is not included:

After - coverage from child pipeline is included:

Example project and MR: alberts-gitlab/test-ruby-cobertura!2

How to set up and validate locally

1. Clone project https://gitlab.com/alberts-gitlab/test-ruby-cobertura locally
2. Pull branch https://gitlab.com/alberts-gitlab/test-ruby-cobertura/-/tree/test-coverage-child-pipeline containing CI and test changes to generate coverage from child pipeline.
3. Create MR in GDK and wait for pipeline to succeed.
4. Verify that the demo_child.rb coverage generated in the child pipeline is not shown in the MR diff.
5. Enable feature flag ci_child_pipeline_coverage_reports.

   Feature.enable(:ci_child_pipeline_coverage_reports)

6. Run a new pipeline on the branch and wait for it to succeed.
7. Verify that the demo_child.rb coverage is now shown in the MR diff.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

doc/development/database/migrations_for_multiple_databases.md

@@ -78,6 +78,30 @@ class AddUserIdAndStateIndexToMergeRequestReviewers < Gitlab::Database::Migratio
 end
 ```
 
+#### Example: Add a new table to store in a single database
+
+1. Define the [GitLab Schema](multiple_databases.md#gitlab-schema) of the table in [`lib/gitlab/database/gitlab_schemas.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/database/gitlab_schemas.yml):
+
+   ```yaml
+   ssh_signatures: :gitlab_main
+   ```
+
+1. Create the table in a schema migration:
+
+   ```ruby
+   class CreateSshSignatures < Gitlab::Database::Migration[2.0]
+     def change
+       create_table :ssh_signatures do |t|
+         t.timestamps_with_timezone null: false
+         t.bigint :project_id, null: false, index: true
+         t.bigint :key_id, null: false, index: true
+         t.integer :verification_status, default: 0, null: false, limit: 2
+         t.binary :commit_sha, null: false, index: { unique: true }
+       end
+     end
+   end
+   ```
+
 ### Data Manipulation Language (DML)
 
 The DML migrations are all migrations that: