Configure Azurite custom service ports

[cristianrgreco]

Summary

• pass configured blob, queue, and table container ports to the Azurite CLI
• strengthen the custom-port regression test to use non-default internal ports and perform blob, queue, and table operations

Verification

• npm run format
• npm run lint
• npm run check-compiles
• npm test -- packages/modules/azurite/src/azurite-container.test.ts -t "should be able to specify custom ports"
• npm test -- packages/modules/azurite/src/azurite-container.test.ts

Test results

• Red: with only the regression test change, the focused custom-port test failed with read ECONNRESET; Azurite logs showed listeners still bound to 10000, 10001, and 10002.
• Green: after passing --blobPort, --queuePort, and --tablePort, the focused regression passed and the complete Azurite module suite passed (9 passed).

Compatibility

This is a backward-compatible bug fix. Default service ports remain unchanged, while explicitly configured service ports now take effect inside the Azurite container.

[netlify]

✅ Deploy Preview for testcontainers-node ready!

Name	Link
🔨 Latest commit	f8aee19
🔍 Latest deploy log	https://app.netlify.com/projects/testcontainers-node/deploys/6a1dabd8a9feda0008156c7b
😎 Deploy Preview	https://deploy-preview-1354--testcontainers-node.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.