Fix: Correct Tor routing configuration - Enable Privacy__EnableTor

## Issue
Previous fix enabled LittleShop__UseTor=true, which tried to route internal
Docker API calls through Tor. Tor correctly rejected these private addresses.

## Root Cause
Two separate Tor configuration flags exist:
1. Privacy__EnableTor - Controls Telegram Bot API calls (external, public)
2. LittleShop__UseTor - Controls LittleShop API calls (internal, private)

## Solution
- Set LittleShop__UseTor=false (internal calls direct - no Tor)
- Set Privacy__EnableTor=true (Telegram API calls via Tor)

## Impact
✅ Telegram Bot API calls now route through Tor (privacy protected)
✅ Internal API calls go direct (no Tor rejection errors)
✅ Proper separation of concerns

## Technical Details
TelegramBotService.cs:77 checks Privacy:EnableTor
Program.cs:63 checks LittleShop:UseTor
These control different HTTP clients for different purposes.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

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

.gitlab-ci.yml

@@ -115,7 +115,8 @@ deploy:vps:
         --network littleshop-network \
         -e ASPNETCORE_URLS=http://+:5010 \
         -e LittleShop__ApiUrl=http://littleshop-admin:8080 \
-        -e LittleShop__UseTor=true \
+        -e LittleShop__UseTor=false \
+        -e Privacy__EnableTor=true \
         -e Privacy__TorSocksHost=tor-gateway \
         -e Privacy__TorSocksPort=9050 \
         localhost:5000/telebot:latest