question about contributing necessary changes for maintaining poetry+uv project

[crockeo]

Hi! I'm working on migrating several projects at my company from poetry to uv. We'd like to do this incrementally, and have encountered some issues. I was interested in contributing some changes back to migrate-to-uv, but I wanted to check if y'all are interested in the following:

• An option to ignore project_already_uses_uv, so one is able to keep running migrate-to-uv after running with --keep-current-data.
• And support for maintaining the existing tool.uv.environments so that we can successfully uv lock with a couple of .whls we vendor only for a small number of platforms.

Let me know and I'll try to get a couple of PRs up!