gh-39962: Docs: Migrate developer walkthrough to Meson
    
<!-- ^ Please provide a concise and informative title. -->
<!-- ^ Don't put issue numbers in the title, do this in the PR
description below. -->
<!-- ^ For example, instead of "Fixes #12345" use "Introduce new method
to calculate 1 + 2". -->
<!-- v Describe your changes below in detail. -->
<!-- v Why is this change required? What problem does it solve? -->
<!-- v If this PR resolves an open issue, please link to it here. For
example, "Fixes #12345". -->

Migrates the developer walkthrough to use meson (on top of conda) for
the easist and most modern setup. Also streamlined the instructions a
bit. Moreover, the main installation page now simply refers to the
developer walkthrough for the dev setup. Finally, a few outdated info
about binaries and linux distro is removed.

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. -->

- [ ] The title is concise and informative.
- [ ] The description explains in detail what this PR is about.
- [ ] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [ ] I have updated the documentation and checked the documentation
preview.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on. For example,
-->
<!-- - #12345: short description why this is a dependency -->
<!-- - #34567: ... -->
    
URL: #39962
Reported by: Tobias Diez
Reviewer(s): Dima Pasechnik, user202729

Author: Release Manager

src/doc/en/developer/git_basic.rst

@@ -206,8 +206,7 @@ Sometimes, a new version of Sage is released while you work on a Git branch.
 
 Let us assume you started ``my_branch`` at commit ``B``. After a while, your
 branch has advanced to commit ``Z``, but you updated ``develop`` (see
-:ref:`section-git-pull-develop`) and now your Git history looks like this (see
-:ref:`section_walkthrough_logs`):
+:ref:`section-git-pull-develop`) and now your Git history looks like this:
 
 .. CODE-BLOCK:: text
 

src/doc/en/developer/review.rst

@@ -17,19 +17,16 @@ Anybody (e.g. you) can do this job for somebody else's PR. This document
 lists things that the reviewer must check before deciding that a PR is
 ready for inclusion into Sage.
 
-You can now begin the review by reading the diff code.
-
 **Check the GitHub checks:** We require all checks have passed.
 
 **Read the diff:** Click "Files changed" tab of the PR. Read through the
 changes of all modified files. We use `pull request reviews
 <https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews>`_.
 You can add comments directly to changed lines.
 
-**Build the code:** (This is optional if the **build and test** check has passed.)
-While you read the code, you can :ref:`rebuild Sage with the new code
-<section-walkthrough-make>`. If you do not know how to **download the code**,
-:ref:`see here <section-workflows-pr-checkout>`.
+**Test the code:** (This is optional if the **build and test** check has passed.)
+Checkout the **code of the PR** following :ref:`see here <section-workflows-pr-checkout>`
+and run the relevant tests.
 
 The following should generally be checked while reading and testing the code: