Extension does not support cross-region failover

- Azure Functions SQL Extension or Extension Bundle Version:
- Is this a deployed or local function: 2 local functions having same name (later we will leverage if fits our use case)
- What type of Database are you using? (Run `SELECT @@VERSION as Version, SERVERPROPERTY('EngineEdition') as EngineEdition` on your database)

Microsoft SQL Azure (RTM) - 12.0.2000.8 Oct 2 2024 11:51:41 Copyright (C) 2022 Microsoft Corporation |  
-- | --

- List any custom settings for your function app. This could be a custom time-out defined specifically for your database server or optional configuration that can be customized for the app defined [here](https://learn.microsoft.com/azure/azure-functions/functions-bindings-azure-sql-trigger?tabs=isolated-process%2Cportal&pivots=programming-language-csharp#optional-configuration).

Issue Description: -

1. We are internal Microsoft team trying to leverage SQL Trigger if we will deploy SQL Trigger to different regions suppose eastus, westus for region fail over scenarios in that case there is no way there change logs will be mutually exclusive and if one function goes down other will continue from the same point. can you please suggest some way out for this. if we deploy it in two diff regions it will result in duplicate records.

No source file, test, or entry point is named. Start by reviewing the Azure SQL trigger's optional configuration and the reported two-region deployment scenario; clarify the required failover semantics and duplicate-record expectations before identifying implementation and tests. Done would require an agreed supported behavior.

Written by the indexing model from the issue text.