`final-state-via` introduced inconsistent behavior for long running operations

[necusjz]

• Package Name: azure-core
• Package Version: 1.24.0
• Operating System: Windows
• Python Version: 3.8.10

Describe the bug
The following PR introduces support for "final-state-via":

• [core] accept 'final-state-via' lro_options in base polling #22713

But, this document says "Azure-AsyncOperation" has higher priority:

• https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/async-operations#url-to-monitor-status

Is there an inconsistency when we have both "Azure-AsyncOperation" and "Location" (with final-state-via) is the header?

To Reproduce
E.g., we have a header like this:

headers:
  ...
  azure-asyncoperation:
  - https://management.azure.com/subscriptions/00000000-0000-0000-0000-000000000000/providers/Microsoft.Network/locations/westcentralus/operations/ca9109a1-acc0-499d-8c9f-9fb75e72050d?api-version=2021-08-01
  ...
  location:
  - https://management.azure.com/subscriptions/00000000-0000-0000-0000-000000000000/providers/Microsoft.Network/locations/westcentralus/operationResults/ca9109a1-acc0-499d-8c9f-9fb75e72050d?api-version=2021-08-01

azure-core==1.21.1 will always go through "azure-asyncoperation", but azure-core==1.24.0 will go through "location", like:

• {CI} Install dependencies using requirements.py3.Linux.txt azure-cli-extensions#4811

Expected behavior
Version upgrades keep consistent behavior for long running operations.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

[azure-sdk]

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Authorization:0.12401441,Docs:0.0746295,Network - Application Gateway:0.045894098'

[iscai-msft]

Hey @necusjz can you send me the swagger so I can confirm this behavior? I'm assuming you have final-state-via: location in your swagger for a PUT request, in which case this behavior is following what the swagger says.

Here's the doc on final-state-via in the bolded note, it states that as long as you follow ARM guidelines, you should not need final-state-via in your swagger. Unfortunately, quite a lot of swaggers had final-state-via incorrectly, and when we decided to actually listen to the swagger in this scenario, we broke some services. If you want to default to azure-asyncoperation, I would fix the swagger by removing the final-state-via from this operation