minor #16628 Reference latest feature branch (Jeroeny)

This PR was merged into the 6.0 branch.

Discussion
----------

Reference latest feature branch

<!--

If your pull request fixes a BUG, use the oldest maintained branch that contains
the bug (see https://symfony.com/releases for the list of maintained branches).

If your pull request documents a NEW FEATURE, use the same Symfony branch where
the feature was introduced (and `6.x` for features of unreleased versions).

-->

Am I correct to think that `6.1` is currently the branch to target feature PRs to ? Or should  `5.x` here be read as a placeholder (instead of literal branchname) and the example be adjusted to `6.x` ?

Commits
-------

c8d9c56 Reference latest feature branch

Author: javiereguiluz

contributing/code/pull_requests.rst

@@ -129,7 +129,7 @@ work:
   </contributing/code/maintenance>` (you may have to choose a higher branch if
   the feature you are fixing was introduced in a later version);
 
-* ``5.x``, if you are adding a new feature.
+* ``6.1``, if you are adding a new feature.
 
   The only exception is when a new :doc:`major Symfony version </contributing/community/releases>`
   (5.0, 6.0, etc.) comes out every two years. Because of the
@@ -152,7 +152,7 @@ topic branch:
 
 .. code-block:: terminal
 
-    $ git checkout -b BRANCH_NAME 5.x
+    $ git checkout -b BRANCH_NAME 6.1
 
 Or, if you want to provide a bug fix for the ``4.4`` branch, first track the remote
 ``4.4`` branch locally:
@@ -281,15 +281,15 @@ while to finish your changes):
 
 .. code-block:: terminal
 
-    $ git checkout 5.x
+    $ git checkout 6.1
     $ git fetch upstream
-    $ git merge upstream/5.x
+    $ git merge upstream/6.1
     $ git checkout BRANCH_NAME
-    $ git rebase 5.x
+    $ git rebase 6.1
 
 .. tip::
 
-    Replace ``5.x`` with the branch you selected previously (e.g. ``4.4``)
+    Replace ``6.1`` with the branch you selected previously (e.g. ``4.4``)
     if you are working on a bug fix.
 
 When doing the ``rebase`` command, you might have to fix merge conflicts.
@@ -502,7 +502,7 @@ PR. Before re-submitting the PR, rebase with ``upstream/5.x`` or
 
 .. code-block:: terminal
 
-    $ git rebase -f upstream/5.x
+    $ git rebase -f upstream/6.1
     $ git push --force origin BRANCH_NAME
 
 .. note::