Add telegram_communication app with dedicated DB routing

- Register TelegramCommunicationConfig in INSTALLED_APPS and add telegram_db to DATABASES
- Define TelegramData model mapped to the messages table
- Fix allow_migrate in ProjectDatabaseRouter: redirect and telegram entries were returning the DB name string (always truthy) instead of a boolean comparison, causing their migrations to bleed into every database
- Add telegram routing to db_for_read, db_for_write, allow_relation, and allow_migrate

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

django_code/apps/telegram_communication/models.py

@@ -1,3 +1,12 @@
 from django.db import models
 
-# Create your models here.
+
+class TelegramData(models.Model):
+    message_id = models.IntegerField(null=False)
+    chat_id = models.IntegerField(null=False)
+    description = models.CharField(max_length=100, null=True)
+    creation_date = models.DateField(blank=True, null=False, verbose_name='Published')
+    expiration_date = models.DateField(blank=True, null=False, verbose_name='Published')
+    class Meta:
+        db_table = 'messages'
+