fix(telegram): align markdown v1 bracket escaping

Purpose of the change:
- Align apprise-go Telegram Markdown v1 rendering with the upstream Python backport and live Telegram client behavior.

How behavior was before:
- Markdown v1 text escaped literal '[' characters.
- Telegram accepted the payload but displayed the backslash in client output.

Why that was a problem:
- Cross-testing against the Python backport and a live Telegram client showed visible bracket escapes in Markdown v1 labels.

What the new change accomplishes:
- Stops escaping literal '[' characters in Telegram Markdown v1 text.
- Keeps MarkdownV2 escaping unchanged.

How it works:
- Removes '[' from the Markdown v1 text replacer.
- Adds a regression test asserting literal brackets remain visible without backslashes.

Author: elibosley

internal/notify/telegram_format_convert.go

@@ -344,7 +344,6 @@ func escapeTelegramMarkdownText(value, markdownMode string) string {
 		"*", "\\*",
 		"_", "\\_",
 		"`", "\\`",
-		"[", "\\[",
 	)
 	return replacer.Replace(value)
 }

internal/notify/telegram_format_test.go

@@ -28,6 +28,17 @@ func TestTelegramConvertsStandardMarkdownToMarkdownV1(t *testing.T) {
 	}
 }
 
+func TestTelegramMarkdownV1DoesNotEscapeLiteralBrackets(t *testing.T) {
+	payload := captureTelegramPayload(t, "tgram://123456:abcdef/7890/?format=markdown&mdv=v1", "**[status]**", "", "markdown")
+
+	if payload["parse_mode"] != "MARKDOWN" {
+		t.Fatalf("expected MARKDOWN parse mode, got %#v", payload["parse_mode"])
+	}
+	if payload["text"] != "*[status]*" {
+		t.Fatalf("expected Telegram markdown body without visible bracket escapes, got %#v", payload["text"])
+	}
+}
+
 func TestTelegramConvertsStandardMarkdownToMarkdownV2(t *testing.T) {
 	payload := captureTelegramPayload(t, "tgram://123456:abcdef/7890/?format=markdown&mdv=v2", "~~Strike~~ **Bold** _Italics_ Text", "", "markdown")