chore: move tqdm to development dependencies

[saturley-hall]

Summary

• move tqdm from the default installation requirements to the dev extra
• update uv.lock so tqdm is selected by extra == 'dev'

Why

AIConfigurator's packaged CLI and SDK do not import tqdm. Its repository uses are limited to Collector and development tools, whose documented and CI environments already install the dev extra.

Regular aiconfigurator installations will no longer receive tqdm; development and test installations remain unchanged.

Validation

• uv lock --check
• verified the base dependency export excludes tqdm
• verified the dev export includes tqdm==4.67.3
• built the wheel and verified its metadata contains Requires-Dist: tqdm>=4.0.0; extra == "dev"
• git diff --check

Summary by CodeRabbit

• Chores
  • Moved the progress display utility to development-only dependencies, reducing the packages installed for production use.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: be4b8508-5089-47d2-8d1a-ea4b6a6d3404

📥 Commits

Reviewing files that changed from the base of the PR and between a8b7b60 and 52ed1f8.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock and included by none

📒 Files selected for processing (1)

• pyproject.toml

📜 Recent review details

🧰 Additional context used

📓 Path-based instructions (1)

**/*

⚙️ CodeRabbit configuration file

**/*: - Prefer applicable inline comments. When the correct fix is clear, small, and limited to the commented diff hunk, include it as a GitHub Suggested Change so the author can apply it with one click.

• Do not use a suggested change when the fix requires broader design choices, multiple files, generated artifacts, unavailable context, or validation that cannot be inferred from the diff.
• If a comment is not directly applicable, state the smallest concrete next step and why a one-click suggestion is not safe.

Files:

• pyproject.toml

🔇 Additional comments (1)

pyproject.toml (1)

54-54: LGTM!

Also applies to: 75-75

---

Walkthrough

The project removes tqdm>=4.0.0 from the main dependencies and adds it to the development dependencies.

Changes

Dependency classification

Layer / File(s)	Summary
Move tqdm to development dependencies pyproject.toml	The development dependency list now includes tqdm>=4.0.0.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Mergeability Score: ⚪ Minimal · up to 52ed1

This change removes tqdm from regular installations while retaining it for development environments; no actionable merge-blocking risk remains after normal checks and review.

Poem

tqdm steps to the dev-side lane,
The runtime list grows light again.
Progress bars wait where builders roam,
The project keeps its leaner home.

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes moving tqdm to development dependencies.
Description check	✅ Passed	The description explains the change, rationale, and validation, but it omits the template headings for reviewer start and related issues.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

_{Comment @coderabbitai help to get the list of available commands.}