CI: add consistency check for packaging metadata files

[Vaishnav88sk]

Problem

Metaflow has both setup.py and setup.cfg; over time dependency/version metadata can diverge.

Proposal

Add a lightweight CI validation step that checks consistency of key metadata across both files, including where applicable:

• Package name
• Version source / version declaration
• Install requirements sections
• Other duplicated metadata fields if relevant

Acceptance criteria

• CI fails on mismatch
• Clear error message pointing to conflicting keys
• Docs note in contributing/testing section

Scope

• Validation logic only
• CI wiring only
• No packaging model change

Contribution

I’d be happy to work on this issue and contribute a PR if this approach sounds good.

[AshishPadala]

Hi, I’d like to work on this issue.

I’ve recently contributed a documentation PR and am now exploring CI-related contributions. This looks like a great opportunity to implement a lightweight validation for packaging metadata consistency.

My initial idea is to add a small script that compares key fields between setup.py and setup.cfg and integrate it into CI.

Please let me know if this approach aligns with expectations.