[MOV] developer/misc: move all pages to a more logical location

Before this commit, the "Developer/Misc" directory of the doc, and
more particularly the "Developer/Misc/Other" sub-directory, was used as
a garbage dump where we moved all the pages that didn't fit elsewhere.
Due to that, interesting and important pages, such as the Coding
Guidelines, were buried in that directory never to be read again by Odoo
developers.

This commit moves most pages under "Misc" one or two levels up to be
located directly under "Developer" hence making them more accessible. A
new "Contributing/Development" directory is added to host the Coding
Guidelines page and soon many other pages.

task-2897143

closes odoo/documentation#2350

X-original-commit: ad374af15d
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>

content/developer/howtos/rdtraining/16_guidelines_pr.rst

@@ -14,7 +14,8 @@ We will start refactoring the code to match to the Odoo coding guidelines. The g
 to improve the quality of the Odoo Apps code.
 
 
-**Reference**: you will find the Odoo coding guidelines in :ref:`reference/guidelines`.
+**Reference**: you will find the Odoo coding guidelines in
+:doc:`/contributing/development/coding_guidelines`.
 
 .. exercise:: Polish your code.
 
@@ -88,7 +89,8 @@ Commit your code:
 
 **Everyone reads your commit messages!**
 
-The commit message is very important, follow the :ref:`Developer guidelines <reference/guidelines/git>`.
+The commit message is very important, follow the :ref:`Git guidelines
+<contributing/development/git_guidelines>`.
 
 
 Push your new branch to your development repository:

content/developer/howtos/rdtraining/B_acl_irrules.rst

@@ -54,7 +54,7 @@ Groups
     The documentation related to this topic can be found in :ref:`the security
     reference <reference/security>`.
 
-    :ref:`The guidelines <reference/guidelines>` document the format and
+    :doc:`/contributing/development/coding_guidelines` document the format and
     location of master data items.
 
 .. admonition:: **Goal**
@@ -481,7 +481,7 @@ or a *visibility* feature before using it:
 
 * *Visibility* features mean a user can still access the model or record
   otherwise, either through an other part of the interface or by :doc:`perform
-  operations remotely using RPC <../../misc/api/external_api>`, things might just not be
+  operations remotely using RPC <../../api/external_api>`, things might just not be
   visible in the web interface in some contexts.
 * *Security* features mean a user can not access records, fields or operations.