Docs: Replace most wiki links with links to new developer docs

Exceptions:
* Links to personal wiki pages
* Pages that are not in the new developer docs yet (like Human Interface Guidelines)
* tools\check_wiki\check_wiki_file_structure.py needs a refactor

doc/python_api/examples/bpy.app.translations.py

@@ -23,8 +23,8 @@ Then, call ``bpy.app.translations.register(__name__, your_dict)`` in your ``regi
 The ``Manage UI translations`` add-on has several functions to help you collect strings to translate, and
 generate the needed python code (the translation dictionary), as well as optional intermediary po files
 if you want some... See
-`How to Translate Blender <https://wiki.blender.org/wiki/Process/Translate_Blender>`_ and
-`Using i18n in Blender Code <https://wiki.blender.org/wiki/Source/Interface/Internationalization>`_
+`How to Translate Blender <https://developer.blender.org/docs/handbook/translating/translator_guide/>`_ and
+`Using i18n in Blender Code <https://developer.blender.org/docs/handbook/translating/developer_guide/>`_
 for more info.
 
 Module References
@@ -35,7 +35,7 @@ Module References
 import bpy
 
 # This block can be automatically generated by UI translations addon, which also handles conversion with PO format.
-# See also https://wiki.blender.org/wiki/Process/Translate_Blender#Translating_non-official_addons
+# See also https://developer.blender.org/docs/handbook/translating/translator_guide/#translating-non-official-add-ons
 # It can (should) also be put in a different, specific py file.
 
 # ##### BEGIN AUTOGENERATED I18N SECTION #####

doc/python_api/rst/include__bmesh.rst

@@ -14,7 +14,7 @@ The features exposed closely follow the C API,
 giving Python access to the functions used by Blender's own mesh editing tools.
 
 For an overview of BMesh data types and how they reference each other see:
-`BMesh Design Document <https://wiki.blender.org/index.php/Dev:Source/Modeling/BMesh/Design>`__.
+`BMesh Design Document <https://developer.blender.org/docs/features/objects/mesh/bmesh/>`__.
 
 
 .. note::

doc/python_api/rst/info_advanced_blender_as_bpy.rst

@@ -13,7 +13,7 @@ allowing ``import bpy`` to be added to any Python script, providing access to Bl
    - A pre-compiled ``bpy`` module is
      `available via PIP <https://pypi.org/project/bpy/>`__.
    - Or you may compile this yourself using the
-     `build instructions <https://wiki.blender.org/w/index.php?title=Building_Blender/Other/BlenderAsPyModule>`__.
+     `build instructions <https://developer.blender.org/docs/handbook/building_blender/python_module/>`__.
 
 
 Use Cases

doc/python_api/rst/info_overview.rst

@@ -91,7 +91,7 @@ They are only loaded on startup if selected from the user preferences.
 The only difference between add-ons and built-in Python modules is that add-ons must contain a ``bl_info`` variable
 which Blender uses to read metadata such as name, author, category and project link.
 The User Preferences add-on listing uses ``bl_info`` to display information about each add-on.
-`See Add-ons <https://wiki.blender.org/index.php/Dev:Py/Scripts/Guidelines/Addons>`__
+`See Add-ons <https://developer.blender.org/docs/handbook/addons/guidelines/>`__
 for details on the ``bl_info`` dictionary.
 
 

doc/python_api/rst/info_tips_and_tricks.rst

@@ -295,7 +295,7 @@ Advantages include:
 
 This is marked advanced because to run Blender as a Python module requires a special build option.
 For instructions on building see
-`Building Blender as a Python module <https://wiki.blender.org/wiki/Building_Blender/Other/BlenderAsPyModule>`__.
+`Building Blender as a Python module <https://developer.blender.org/docs/handbook/building_blender/python_module/>`__.
 
 
 Python Safety (Build Option)