fix: new clippy warnings

[Vaiz]

📌 Summary

This PR fixes new clippy warnings. I also had to enable at least one schema by default, but I think it's a good change, and makes it easier to use the crate.

Sorry for mixed PR, these other issues were causing troubles when I tried to fix clippy warnings.

🔍 Related Issues

In PR #63 , ci is failing because of these new errors

• Fixes #

✨ Changes Made

- added rust-mcp-sdk as dev-dependency to rust-mcp-macros
- strategically placed #[cfg(any(feature = "2025_03_26", not(feature = "2024_11_05")))] in a few places to fix compilation errors
- rust-mcp-transport is not optional anymore

• fixed clippy warnings

🛠️ Testing Steps

💡 Additional Notes

[Vaiz]

Technically, now when all clippy warnings are fixed, I can rollback other changes.
Fill free to merge only c3c2557 commit.

[hashemix]

Thanks @Vaiz , really appreciate the help 🥇

Sorry for mixed PR, these other issues were causing troubles when I tried to fix clippy warnings.

Yea I noticed, I would prefer to avoid mixing concerns in same PR, there are some unrelated to the clippy warnings , those might be better suited for a separate issue and PR.

would you mind updating pr to have changes related to clippy warnings? (i.e c3c2557)

If you revert other changes and only keep c3c2557 , will we have any build error? 🤔

[Vaiz]

Yea I noticed, I would prefer to avoid mixing concerns in same PR, there are some unrelated to the clippy warnings , those might be better suited for a separate issue and PR.

would you mind updating pr to have changes related to clippy warnings? (i.e c3c2557)

done

If you revert other changes and only keep c3c2557 , will we have any build error? 🤔

clippy errors should be gone, but other issues, related to not working combinations of features, will remain

[hashemix]

Thanks @Vaiz , I will merge it once you resolve the conflicts

other compilation error you mentioned , it does not happen normally when we run cargo build --workspace I think happens only when we call cargo build --all-targets , that I don't think is a blocker but better to be resolved, perhaps in a separate pr

[Vaiz]

updated PR.

other compilation error you mentioned , it does not happen normally when we run cargo build --workspace I think happens only when we call cargo build --all-targets , that I don't think is a blocker but better to be resolved, perhaps in a separate pr

I encountered these error when I had tried to run cargo clippy --fix, you should see the same.

[hashemix]

Looks good!
Thanks so much for your contributions and quick responses! 🥇