Render reminder and jamaat time in bot timezone

[escalopa]

Summary

• use each bot's configured timezone when rendering prayer and jamaat clock times in soon reminders
• keep markdown parenthesis escaping for message safety
• wire bot config into SoonReminder to resolve timezone per bot

Testing

• go test ./... (serverless/reminder)

[github-actions]

Terraform Plan — dev

data.archive_file.dispatcher_zip: Reading...
data.archive_file.reminder_zip: Reading...
data.archive_file.loader_zip: Reading...
data.archive_file.loader_zip: Read complete after 0s [id=10158ba6abce70b709908945413eb44e0e542992]
data.archive_file.reminder_zip: Read complete after 0s [id=8daa862fd8669815907d6bee0a5e8e972f2b9b20]
data.archive_file.dispatcher_zip: Read complete after 0s [id=813a6efc989d458d6b360ccd42959233dd0261bd]
yandex_storage_bucket.bucket: Refreshing state... [id=prayer-bot-bucket-dev]
yandex_iam_service_account.trigger_sa: Refreshing state... [id=ajem0gaf8no06keub59n]
yandex_resourcemanager_folder_iam_member.dispatcher_sa_invoker: Refreshing state... [id=b1g4bpqj67cilsh4637j/functions.functionInvoker/system:allUsers]
yandex_ydb_database_serverless.ydb: Refreshing state... [id=etncm1ma7um66odosquf]
yandex_iam_service_account.reminder_sa: Refreshing state... [id=ajebutnaqriod6u0cuv1]
yandex_iam_service_account.dispatcher_sa: Refreshing state... [id=aje2d65lii6aegt6lknu]
yandex_iam_service_account.loader_sa: Refreshing state... [id=ajesnbctlpiumgbvpv11]
yandex_resourcemanager_folder_iam_member.reminder_sa_ydb: Refreshing state... [id=b1g4bpqj67cilsh4637j/ydb.editor/serviceAccount:ajebutnaqriod6u0cuv1]
yandex_iam_service_account_static_access_key.reminder_sa_keys: Refreshing state... [id=ajedkdvbr0kr3jjsojd1]
yandex_resourcemanager_folder_iam_member.trigger_sa_invoker: Refreshing state... [id=b1g4bpqj67cilsh4637j/functions.functionInvoker/serviceAccount:ajem0gaf8no06keub59n]
yandex_resourcemanager_folder_iam_member.dispatcher_sa_ydb: Refreshing state... [id=b1g4bpqj67cilsh4637j/ydb.editor/serviceAccount:aje2d65lii6aegt6lknu]
yandex_iam_service_account_static_access_key.dispatcher_sa_keys: Refreshing state... [id=ajet4icfvq94u1p6cfsc]
yandex_iam_service_account_static_access_key.loader_sa_keys: Refreshing state... [id=aje0el2tlj008n17efca]
yandex_resourcemanager_folder_iam_member.loader_sa_storage: Refreshing state... [id=b1g4bpqj67cilsh4637j/storage.viewer/serviceAccount:ajesnbctlpiumgbvpv11]
yandex_resourcemanager_folder_iam_member.loader_sa_ydb: Refreshing state... [id=b1g4bpqj67cilsh4637j/ydb.editor/serviceAccount:ajesnbctlpiumgbvpv11]
yandex_function.reminder_fn: Refreshing state... [id=d4egvuna854hcslsqq4b]
yandex_function.loader_fn: Refreshing state... [id=d4e54dhcpktpbk6ldrah]
yandex_function.dispatcher_fn: Refreshing state... [id=d4e3e9cn2l0it3kddr7f]
yandex_function_trigger.reminder_trigger: Refreshing state... [id=a1sncjtml7mu93qdvrln]
yandex_function_trigger.loader_trigger: Refreshing state... [id=a1s0ont98ata0r677aco]

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # yandex_function.reminder_fn will be updated in-place
  ~ resource "yandex_function" "reminder_fn" {
        id                 = "d4egvuna854hcslsqq4b"
        name               = "reminder-fn"
        tags               = []
      ~ user_hash          = "d42e55f1ec521ab9b5100a3bb86de53b" -> "446430f95c9b23236e58cd28ed506073"
        # (13 unchanged attributes hidden)

        # (2 unchanged blocks hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Note: You didn't use the -out option to save this plan, so Terraform can't
guarantee to take exactly these actions if you run "terraform apply" now.