Suggest importable type that differs slightly

[GTimothy]

This PR proposes to add types that differ slightly to suggested imports.
Previous discussion of this topic here: #72641 and in this PR: #72988
If that is still of interest, a discussion may be needed to limit or expand the included list.

I followed the suggestions in #72988.
In this initial change, the list is simply expanded to types with one char edit distance.
The tests are based on the tests by @chrissimpkins in #72988.

I added a is_exact_match field to ImportSuggestion to eventually modify the suggestion text accordingly, but for now it is ignored.

fn test_layout(_x: LayOut){}
//~^ ERROR: cannot find type `LayOut` in this scope

error[E0425]: cannot find type `LayOut` in this scope
  --> $DIR/libstd.rs:3:20
   |
LL | fn test_layout(_x: LayOut){}
   |                    ^^^^^^ not found in this scope
   |
help: consider importing this struct
   |
LL + use std::alloc::Layout;
   |  

for a more complex case:

fn test_systemtime(_x: Systemtime){}
//~^ ERROR: cannot find type `Systemtime` in this scope

struct SystemTome{}
mod st{
    struct SystemTame{}
}

error[E0425]: cannot find type `Systemtime` in this scope
  --> $DIR/libstd.rs:428:24
   |
LL | fn test_systemtime(_x: Systemtime){}
   |                        ^^^^^^^^^^
...
LL | struct SystemTome{}
   | ----------------- similarly named struct `SystemTome` defined here
   |
help: a struct with a similar name exists
   |
LL - fn test_systemtime(_x: Systemtime){}
LL + fn test_systemtime(_x: SystemTome){}
   |
help: consider importing this struct
   |
LL + use std::time::SystemTime;
   |

SystemTame's edit-distance is 2, so not suggested.

[GTimothy]

I see from the 247 failed tests that 1-edit difference is too big for small names. 'net' should probably NOT be suggested to replace 'new'...