[FIX] developer/*: consistent code-block language specification

Part-of: odoo/documentation#3001

content/administration/odoo_sh/getting_started/first_module.rst

@@ -141,7 +141,7 @@ Uncomment the content of the files:
   the manifest of your module, including for instance its title, description and data files to load.
   You just need to uncomment the access control list data file:
 
-  .. code-block:: xml
+  .. code-block:: python
 
     # 'security/ir.model.access.csv',
 

content/developer/howtos/accounting_localization.rst

@@ -23,7 +23,7 @@ Building a localization module
 
 The structure of a basic ``l10n_XX`` module may be described with the following :file:`__manifest__.py` file:
 
-.. code-block:: py
+.. code-block:: python
 
     {
         "name": "COUNTRY - Accounting",
@@ -345,7 +345,7 @@ Accounting reports should be added via a separate module `l10n_XX_reports` that
 Basic :file:`__manifest__.py` file for such a module looks as following:
 
 
-.. code-block:: py
+.. code-block:: python
 
     {
         "name": "COUNTRY - Accounting Reports",

content/developer/reference/backend/testing.rst

@@ -202,7 +202,7 @@ Besides tags you can also specify specific modules, classes or functions to
 test. The full syntax of the format accepted by :option:`--test-tags <odoo-bin --test-tags>`
 is:
 
-.. code-block::
+.. code-block:: text
 
     [-][tag][/module][:class][.method]
 

content/developer/reference/frontend/assets.rst

@@ -63,7 +63,7 @@ with a dedicated `assets` key which contains a dictionary. The dictionary maps
 bundle names (keys) to the list of files they contain (values). It looks
 like this:
 
-.. code-block:: py
+.. code-block:: python
 
     'assets': {
         'web.assets_backend': [

content/developer/reference/frontend/framework_overview.rst

@@ -328,7 +328,7 @@ browser.
 
 Example:
 
-.. code-block:: js
+.. code-block:: javascript
 
    import { evaluateExpr } from "@web/core/py_js/py";
 

content/developer/reference/frontend/registries.rst

@@ -161,11 +161,11 @@ direct child. This component is basically a live representation of the ordered
 list of components registered in the main components registry.
 
 API
-    .. code-block::
+    .. code-block:: text
 
         interface {
-          Component: Owl Component class
+            Component: Owl Component class
-          props?: any
+            props?: any
         }
 
 
@@ -243,7 +243,7 @@ with the following three keys:
 
 For example:
 
-.. code-block:: js
+.. code-block:: javascript
 
     import { registry } from "@web/core/registry";
 
@@ -258,7 +258,7 @@ For example:
 
 The systray registry is an ordered registry (with the `sequence` number):
 
-.. code-block:: js
+.. code-block:: javascript
 
     const item = {
         Component: MySystrayItem
@@ -291,7 +291,7 @@ The user menu calls all the functions defining items every time it is opened.
 
 Example:
 
-.. code-block:: js
+.. code-block:: javascript
 
     import { registry } from "@web/core/registry";
 

content/developer/reference/frontend/services.rst

@@ -902,7 +902,7 @@ API
 
     remove the value with the given key from the :ref:`user context<frontend/framework/user_context>`
 
-    .. code-block:: js
+    .. code-block:: javascript
 
       userService.removeFromContext("isFriend")
 
@@ -914,6 +914,6 @@ API
 
     check if the user is part of a group
 
-    .. code-block:: js
+    .. code-block:: javascript
 
       const isInSalesGroup = await userService.hasGroup("sale.group_sales")