Support creating iterations under a parent path

[gbclw]

Summary

Extend create_iterations to support creating iterations under a specific parent path (e.g. Testproject\2026). Currently iterations are always created at the root level, making it impossible to organize sprints under (for example) year folders.

Tools

Extend the following tool with a parentPath parameter:

create_iterations: Create iterations under a specified parent path in the iteration tree.

Endpoint: POST https://dev.azure.com/{organization}/{project}/_apis/wit/classificationnodes/iterations/{parentPath}?api-version=7.2-preview.2

Add an optional parentPath parameter to each iteration object. When provided, the iteration is created as a child of that path. When omitted, behavior remains unchanged (created at root).

Example input:
{
"project": "Testproject",
"iterations": [
{
"iterationName": "Sprint 315",
"parentPath": "Testproject\\2026",
"startDate": "2026-04-15T00:00:00Z",
"finishDate": "2026-04-28T00:00:00Z"
}
]
}

Rules

1. Adhere strictly to existing project standards and coding conventions.
2. Ensure each tool exposes all API parameters (required and optional).
3. Use the official Azure DevOps Node API to interact with the APIs.

[gbclw]

@danhellem now that this has been moved from an issue to a discussion under "backlog of suggestions": is there any indication of if or when this might be picked up? Happy to contribute a PR if that would help move things along.