Taiga: refactor service naming & resource limits

Add CPU/memory/pids limits for taiga, async, front, gateway, events, async-rabbitmq, events-rabbitmq, manager, and protected. Align manager service usage (was taiga-manage) in admin tasks and inits compose. Switch to variable-driven service names (TAIGA_* vars), add container_name patterns, normalize volume mappings via TAIGA_VOLUME_STATIC/MEDIA, fix depends_on to use TAIGA_* vars, and set RabbitMQ hostnames from vars. Remove obsolete Development.md.

Conversation reference: https://chatgpt.com/share/68da83b7-0cb4-800f-9702-d8a2d4ebea71  (replace with this chat’s share link)

roles/web-app-taiga/templates/docker-compose-inits.yml.j2

@@ -1,5 +1,7 @@
 {% include 'roles/docker-compose/templates/base.yml.j2' %}
-  taiga-manage:
+{% set service_name = TAIGA_MANAGER_SERVICE %}
+  {{ service_name }}:
+    container_name: {{ TAIGA_CONTAINER }}-{{ service_name }}
 {% include 'roles/docker-container/templates/base.yml.j2' %}
     image: taigaio/taiga-back:latest
     environment:
@@ -8,8 +10,8 @@
 {% include 'roles/docker-container/templates/networks.yml.j2' %}
     entrypoint: "python manage.py"
     volumes:
-      - static-data:/taiga-back/static
-      - media-data:/taiga-back/media
+      - static-data:{{ TAIGA_VOLUME_STATIC }}
+      - media-data:{{ TAIGA_VOLUME_MEDIA }}
       # - ./config.py:/taiga-back/settings/config.py
 {% include 'roles/docker-compose/templates/networks.yml.j2' %}
   taiga: