Fix misplaced content in GitLab docs (#6654)

* Fix misplaced content in GitLab docs

Part of the bullet list that should go under the "Stack Trace Linking" heading is instead under the "Code owners" heading (showing up as a txt code block), and this last heading is also repeating twice.

In this changeset I fixed the aforementioned problems, and made some minor changes to the text to avoid repetition.

Cheers!

* Update src/docs/product/integrations/source-code-mgmt/gitlab/index.mdx

---------

Co-authored-by: Shana Matthews <shana.l.matthews@gmail.com>

Author: EQuineOntology

src/docs/product/integrations/source-code-mgmt/gitlab/index.mdx

@@ -136,8 +136,10 @@ Stack trace linking takes you from a file in your Sentry stack trace to that sam
    - **repo** (required): This is the GitLab project associated with the Sentry project above. If you have more than one GitLab project being used per Sentry project, you'll need multiple code mappings.
    - **branch** (required): This is the default branch of your code we fall back to if you do not have commit tracking set up.
    - **stack trace root** and **source code root** (optional):
-
-     1. If the file path in your Sentry stack trace frame matches the path to your source code, you do not need to set these values.
+     - If the file path in your Sentry stack trace frame matches the path to your source code, you don't need to set these values.
+         - For example, if everything after the branch (`main`) matches the file path of `code.py` using a source code path of `https://gitlab.com/murdith-group/issa-project/-/blob/main/code.py`, you don't need to set either `stack trace root` or `source code root`
+     - If the file path in your Sentry stack trace frame doesn't match the path to your source code, you will need to replace the `stack_root` part of the file path with your `source_root` to make the file path match the source code path.
+         - For example, to get `src/code.py` to match `code.py` when the source code path is `https://gitlab.com/murdith-group/issa-project/-/blob/main/code.py`, change the `stack trace root` to be set as `src/`, and leave `source code root` empty.
 
 ### Suspect Commits
 
@@ -147,13 +149,6 @@ Once you've set up stack trace linking, Sentry can use information from your sou
 
 Learn about setting up this functionality in [Suspect Commits](/product/issues/suspect-commits/).
 
-### Code Owners
-
-        - ex. For example, everything after the branch (`main`) matches the file path of `code.py` using a source code path of `https://gitlab.com/murdith-group/issa-project/-/blob/main/code.py` so you don't need to set a **stack trace root** and **source code root**.
-
-     1. If the file path in your Sentry stack trace frame doesn't match the path to your source code, you will need to replace the **stack_root** part of the file path with your **source_root** to make the file path match the source code path.
-        - ex. For example, to get `src/code.py` to match `code.py` when the source code path is `https://gitlab.com/murdith-group/issa-project/-/blob/main/code.py`, change the **stack trace root** to be set as `src/`, and leave **source code root** empty.
-
 ### Code Owners
 
 <Note>