MAINT: LinkAhead rename

Summary

• in User Documentation (online, readmes, other doc folders)
• deprecate old imports
• add new ways to import
• search and replace in remaining files; change only if it has no functional implications
• Replace 'docs.indiscale.com` by new domain name. new issue

Test Environment

pipelines

Check List for the Author

Please, prepare your MR for a review. Be sure to write a summary and a focus and create gitlab comments for the reviewer. They should guide the reviewer through the changes, explain your changes and also point out open questions. For further good practices have a look at our review guidelines

• All automated tests pass
• Reference related issues
• Up-to-date CHANGELOG.md (or not necessary)
• Up-to-date JSON schema (or not necessary)
• Appropriate user and developer documentation (or not necessary)
  • How do I use the software? Assume "stupid" users.
  • How do I develop or debug the software? Assume novice developers.
• Annotations in code (Gitlab comments)
  • Intent of new code
  • Problems with old code
  • Why this implementation?

Check List for the Reviewer

• I understand the intent of this MR
• All automated tests pass
• Up-to-date CHANGELOG.md (or not necessary)
• Appropriate user and developer documentation (or not necessary)
• The test environment setup works and the intended behavior is reproducible in the test environment
• In-code documentation and comments are up-to-date.
• Check: Are there specifications? Are they satisfied?

For further good practices have a look at our review guidelines.

src/doc/gallery/curator-permissions.rst

@@ -26,27 +26,27 @@ The curator role
 ~~~~~~~~~~~~~~~~
 
 First, a ``curator`` role is created with a meaningful description. We'll use
-``caosdb_admin.py`` for this which leads to the following command:
+``linkahead_admin.py`` for this which leads to the following command:
 
 .. code:: console
 
-   $ caosdb_admin.py create_role "curator" "A user who is permitted to create new Records, Properties, and RecordTypes but who is not allowed to change the core data model."
+   $ linkahead_admin.py create_role "curator" "A user who is permitted to create new Records, Properties, and RecordTypes but who is not allowed to change the core data model."
 
 To actually see how this role's permissions change, we also need a user with
 this role. Assume you already have created and activated (see
 :doc:`Administration <../administration>`) a ``test_curator`` user, then
-``caosdb_admin.py`` is used again to assign it the correct role:
+``linkahead_admin.py`` is used again to assign it the correct role:
 
 .. code:: console
 
-   $ caosdb_admin.py add_user_roles test_curator curator
+   $ linkahead_admin.py add_user_roles test_curator curator
 
 .. note::
 
    The ``test_curator`` user shouldn't have administration privileges, otherwise
    the below changes won't have any effect.
 
-The core data model and caosdb-advanced-user-tools
+The core data model and linkahead-advanced-user-tools
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 In principle, the following script works with any data model defined in a json
@@ -62,7 +62,7 @@ Clone the schemata into the same directory containing the below script via
    $ git clone https://github.com/leibniz-zmt/zmt-metadata-schema.git
 
 Furthermore, we'll need the `LinkAhead Advanced User Tools
-<https://gitlab.com/caosdb/caosdb-advanced-user-tools>`_ for loading the
+<https://gitlab.com/linkahead/linkahead-advanced-user-tools>`_ for loading the
 metadata schemata from the json files, so install them via
 
 .. code:: console
@@ -76,7 +76,7 @@ Users with the ``curator`` role should be able to have any permission for all
 entities by default. The exceptions for the core data model entities will be set
 with the script below. These default settings are best done via the
 ``global_entities_permissions.xml`` config file (see the `server documentation
-<https://docs.indiscale.com/caosdb-server/permissions.html#how-to-set-permissions>`_). Simply
+<https://docs.linkahead.org/linkahead-server/permissions.html#how-to-set-permissions>`_). Simply
 add the following line to the file
 
 .. code:: xml
@@ -89,7 +89,7 @@ beginning) **with priority**. This ensures, that no normal user is allowed to
 overrule these permissions (since it is granted with priority), but it can still
 be denied for the core data model entities by a **deny** rule with priority. See
 the server documentation on `permission
-calculation <https://docs.indiscale.com/caosdb-server/permissions.html#permission-calculation>`_
+calculation <https://docs.linkahead.org/linkahead-server/permissions.html#permission-calculation>`_
 for more information on which permission rules can or can't be overruled.
 
 Your complete ``global_entities_permissions.xml`` might then look like