[IMP] developer: improve navigation in top-level pages

Prior to this commit, users had to either know in advance or guess the
location of the content they were looking for. Top-level pages of the
"Developer" section of the documentation, in particular the "Developer"
page itself, were listing their sub-pages without directions for users.

This commit brings the following changes to improve the navigation:
- add directions for users on the "Developer" page and list the three
  main categories of developer documentation ("Tutorials", "How-to
  guides", and "Reference") with explanations of their content and
  target audience;
- add categories for content cards on the "Tutorials" and "How-to
  guides" pages, and fine-tune the toctree of the "Reference" page to
  more easily locate specific topics;
- clarify what are the "Python framework" and the "JavaScript framework"
  by relabelling them to "Server framework" and "Web framework" on
  top-level pages, as some users were confused to find that the JS
  framework was not responsible for the server, and others that the
  documentation for QWeb template is located in the Python documentation;
- extract the "Setup guide" from the "Getting started" tutorial and
  rename the latter to "Server framework 101" to allow reusing the setup
  guide in other tutorials and make clear that the "Server framework 101"
  tutorial is not about the Web framework.

task-3802536

closes odoo/documentation#8712

X-original-commit: 7f623b6ad5
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Co-authored-by: Valeriya (vchu) <vchu@odoo.com>

content/developer/tutorials/restrict_data_access.rst

@@ -3,11 +3,9 @@ Restrict access to data
 =======================
 
 .. important::
-   This tutorial is an extension of the :doc:`getting_started` tutorial. Make sure you have
+   This tutorial is an extension of the :doc:`server_framework_101` tutorial. Make sure you have
    completed it and use the `estate` module you have built as a base for the exercises in this
-   tutorial. Fetch the branch `{BRANCH}-core` from the `technical-training-solutions
-   <https://github.com/odoo/technical-training-solutions/tree/{BRANCH}-core>`_ repository if you
-   want to start from a clean base.
+   tutorial.
 
 So far we have mostly concerned ourselves with implementing useful features.
 However in most business scenarios *security* quickly becomes a concern:
@@ -17,7 +15,7 @@ currently,
   update or delete properties, property types, or property tags.
 * If ``estate_account`` is installed then only agents allowed to interact
   with invoicing can confirm sales as that's necessary to :ref:`create an
-  invoice <tutorials/getting_started/14_other_module/create>`.
+  invoice <tutorials/server_framework_101/13_other_module/create>`.
 
 However:
 
@@ -142,7 +140,7 @@ Access Rights
       real-estate application.
     - Real-estate agents will not be able to update the property types or tags.
 
-Access rights were first introduced in :ref:`tutorials/getting_started/05_securityintro`.
+Access rights were first introduced in :doc:`server_framework_101/04_securityintro`.
 
 Access rights are a way to give users access to models *via* groups: associate
 an access right to a group, then all users with that group will have the access.