Add Python mock-api tests for postPagingLroWithBody ARM LRO paging scenario

[Copilot]

Adds Python SDK coverage for the postPagingLroWithBody ARM scenario updated in Azure/typespec-azure#4991, which declares the LRO final result (ArmLroLocationHeader<FinalResult = ProductListResult>) for a paged LRO POST that takes a request body.

Changes

• Spec dependency: bumped @azure-tools/azure-http-specs to 0.1.0-alpha.44-dev.4, the first published version containing the fix.
• Sync test (mock_api/azure/test_azure_arm_operationtemplates.py): exercises begin_post_paging_lro_with_body with a VnetProfile body and asserts the two-page result.
• Async test (mock_api/azure/asynctests/test_azure_arm_operationtemplates_async.py): async counterpart.
• Changelog: internal entry for @typespec/http-client-python.

def test_lro_paging_begin_post_paging_lro_with_body(client):
    result = client.lro_paging.begin_post_paging_lro_with_body(
        resource_group_name=RESOURCE_GROUP_NAME,
        product_name="default",
        body=models.VnetProfile(vnet_id="vnet1"),
    ).result()
    items = list(result)
    assert [i.name for i in items] == ["product1", "product2"]

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
1 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[msyyc]

@copilot Follow https://github.com/microsoft/typespec/blob/63abfc2113f2751cb482daa8aeb6f519ef07662d/.github/skills/python-sdk-spector-mock-api-tests/SKILL.md to add python test case for Azure/typespec-azure#4632 in this PR

[azure-sdk-automation]

You can try these changes here

🛝 Playground	🌐 Website	🛝 VSCode Extension

[Copilot]

@copilot Follow https://github.com/microsoft/typespec/blob/63abfc2113f2751cb482daa8aeb6f519ef07662d/.github/skills/python-sdk-spector-mock-api-tests/SKILL.md to add python test case fo...

Added Python mock-api tests (sync + async) for the operation-templates scenarios introduced in Azure/typespec-azure#4632:

• Lro.getLro (GET LRO via markAsLro)
• Paging.postActionPaging (POST @list)
• Paging.markAsPageable (ArmListSinglePageByParent)
• Legacy.routedGet (RoutedOperations custom route)
• Legacy.createOrReplaceOptionalBody (with and without body)

All 44 operation-templates tests pass locally against the Spector mock server.

One note on postActionPaging: with the current pinned TCGC (~0.70.0), pagingMetadata.nextLinkSegments isn't populated for a synchronous POST @list action, so the generated client's extract_data returns None as the continuation token and doesn't follow the response nextLink (only page 1 is returned). I kept that test forward-compatible by validating the page-1 contents rather than hard-coding the single-page count, so it will still pass once the emitter/TCGC follows the next link. Let me know if you'd prefer I instead assert the full two-page result and track the pagination gap separately.