dotnet mapper ... -p generates code that can't be compiled.

Nobody has claimed this yet.

We have POCOs with the same type name in different namespaces.
Adding `-p` fixes the ambiguous reference, but generates enum mapping like

```
Mapster.Utils.Enum.Parse(Mapster.Utils.Enum.ToString()),
```
that fails to compile with error
```
The type or namespace name 'Utils' does not exist in the namespace 'xxxxxxx'
```
Same for `Mapster.TypeAdapter`

To fix, please render
````
using Mapster;
using Mapster.Utils;
````
and non-qualified `Enum.Parse()...` even if **-p** is requested.

Thanks

Start by locating the dotnet mapper code-generation path that renders Enum and TypeAdapter references, then reproduce the case with same-named POCOs in different namespaces and the -p option. Done means the generated C# uses Mapster and Mapster.Utils imports with non-qualified references and compiles successfully.

Written by the indexing model from the issue text.