The Unity bug that caused this has been fixed by Unity. The Path Painter workaround described below was removed in Path Painter v2.1.5. Make sure you use the latest patch for your Unity version.
Please get in contact if you still need help with this.
This is due to a known Unity bug.
First of all, if you are a Path Painter user or affected by this, please vote for this issue: https://issuetracker.unity3d.com/issues/found-plugins-with-same-names-error-is-thrown-for-the-microsoft-extensions-logging-package-when-building-on-android-platform
(Yes, the issue in issuetracker is specific to a Microsoft package, but that's just the way Unity QA handles it. I.e.: they keep open that Microsoft package specific issue and close reports that point to the root issue as duplicates at the moment. This may have changed by the time you read this.)
There is a temporary solution in Path Painter II introduced in v2.1.4 to prevent the Unity bug. You can apply it from the menu:
Note: You only need to use the fix if you are seeing the "Found plugins with same names" errors pointing to Path Painter files. The fix disables Path Painter features affected by the bug, and as a result, the Path Painter menu may disappear when you change your scripting environment. You will need to reimport Path Painter using the Package Manager, if that happens, and you may need to reapply the fix as well.
Please submit a support request if you have any questions or comment.