Fix ProductApi association race during API publishing

[Copilot]

APIs and Products were published concurrently, allowing ProductApi associations to run before asynchronous API provisioning completed. This caused API not found errors and Swagger/OpenAPI publish timeouts, particularly with overrides.

Changes

• Split tier-2 publishing into ordered waves:
  1. Regular APIs
  2. MCP APIs
  3. Products and other non-API resources
• Preserve parallel publishing within each wave.
• Add regression coverage ensuring Products wait for API publication to complete.

• Fixes Bug: Swagger API publish times out with overrides; ProductApi association race condition #101

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Aleksey Zheltov (Alexey-Zheltov)]

Tested this locally in a dev container on top of latest main:

• npm ci / npm run build — clean, no errors
• npm test — all 60 test files passed, 1321/1321 tests passed
• Confirmed in the logs that the new regression coverage exercises Products waiting for API publication to complete, including the failure path for a ProductApi association (Failed to create ProductApi association my-product/petstore: Error: Association PUT failed handled gracefully)

Also merged this together with #255 into a combined branch to check for conflicts — no conflicts (this PR only touches src/services/publish-service.ts, #255 only touches src/clients/apim-client.ts), and all 1323 tests still pass on the combined branch.

LGTM from a testing standpoint 👍

[Aleksey Zheltov (Alexey-Zheltov)]

LGTM Products correctly wait for API publishing to complete in tier 2, verified locally with full test suite passing and no conflicts with #255.