How to generate "correct" paths for types in replacement snippets

I'm writing a new lint (and have written one before, too), where the suggested replacement code needs to reference a type where it's non-obvious how the type has been imported into scope.

Is there a handy helper somewhere for "Given this type, give me the best way this code could reference it"? i.e. if the type is imported into scope, use its bare name, or if the module which defines it is in scope, reference it as module::Type, or if not, use ::fully::qualified::Type?

If not, are there any pointers for how I might go about implementing such a thing?

Thanks!

Start by examining the existing Clippy lint infrastructure for suggested replacement code and how types are represented in scope. The issue names no files, tests, or entry points; done would require determining whether a helper exists or defining and validating an approach for choosing imported, module-qualified, or fully qualified type paths.