fix(sources): log PKG-INFO stub creation at INFO

[ryanpetrello]

Use INFO for expected stub creation in ensure_pkg_info().

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Repository: python-wheel-build/fromager/.coderabbit.yaml
• Review profile: CHILL
• Plan: Advanced
• Run ID: 02a14efe-3d69-46e4-9924-82c8f39ce55d

📥 Commits

Reviewing files that changed from the base of the PR and between 5f5bbd9 and c4ccc98.

📒 Files selected for processing (1)

• src/fromager/sources.py

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

When PKG-INFO is missing, ensure_pkg_info now logs the message at info level instead of warning. Stub-file creation and return behavior are unchanged.

Priority: ⬇️ Low

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

Merge Risk: ⚪ Minimal · up to c4ccc

The expected missing-PKG-INFO message is now logged at info level, with stub behavior unchanged; no actionable merge-blocking risk is identified.

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the change: logging PKG-INFO stub creation at INFO level.
Description check	✅ Passed	The description accurately states that ensure_pkg_info() uses INFO for expected stub creation.
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.

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[rd4398]

LGTM

[mergify]

This pull request does not currently match the merge queue conditions, so it cannot be queued from here. The box comes back if it matches again.