[evidence] spark logs spark-telegram-bot returns "No logs yet" even when bot is running - wrong log file path

[Acone8]

Before: spark logs spark-telegram-bot returns "No logs yet for spark-telegram-bot:primary at ~/.spark/logs/spark-telegram-bot/primary.log" even when the bot is actively running and logging to process.log.

After fix: spark logs spark-telegram-bot correctly falls back to process.log when primary.log does not exist, showing the actual running bot logs.

Root cause: DEFAULT_PRIMARY_TELEGRAM_PROFILE is "primary" so cmd_logs looks for primary.log, but bots started without an explicit profile write to process.log (DEFAULT_TELEGRAM_PROFILE = "default").

Repro steps:

1. Start spark-telegram-bot normally with spark start telegram-starter
2. Run spark logs spark-telegram-bot
3. Observe: No logs yet for spark-telegram-bot:primary at primary.log
4. Check ~/.spark/logs/spark-telegram-bot/ - actual logs are in process.log not primary.log