Security concerns due to `lazy-imports` package in the python generator

I don't want to be a buzzkill or step on someone's toes. Still, with that change, you are potentially pushing a dependency with nine GitHub stars and two maintainers into millions of micro-services. I'd reconsider...

Originally posted by @Thommy257 in https://github.com/OpenAPITools/openapi-generator/issues/21486#issuecomment-3220495818

Hi all,

In your latest release, v7.15.0, you included a package called lazy-imports required to run the generated API client code (see https://github.com/OpenAPITools/openapi-generator/pull/21486). Due to a lack of maintenance and public verification, this package poses a significant security risk. I suggest undoing this change or internalising it into openapi-generator.

Also, this PR probably broke many CI/CD pipelines. And for those that didn't break, many microservices got silently injected with a package not verified by a large open source community.

Start by reviewing PR 21486 and the v7.15.0 Python generator changes that introduced lazy-imports. Trace how the package becomes a runtime dependency of generated API clients, then determine whether the dependency is removed or internalized and verify generated clients no longer require the unverified package.