Improve user guidance for naming conflicts in Simple Renaming

[Weisl]

Summary:

When using the trim or search/replace functions in Simple Renaming (Blender 5.0.1), users may see "no objects renamed" or encounter unexpected behavior due to Blender’s automatic suffixing (e.g., .001) when duplicate names exist. This is not a bug in the addon, but rather a result of Blender’s internal naming rules. Users are often confused and assume the tool is broken.
Steps to Reproduce:

Have objects with duplicate names in the scene (e.g., Chest_Plate and Chest_Plate.001).
Select the objects and attempt to use trim or search/replace.
The addon reports no changes, and the suffix remains.
Expected Behavior:

The addon should clearly inform the user that a naming conflict exists and explain that Blender’s automatic suffixing is interfering. Ideally, it should suggest renaming conflicting objects to unique names before proceeding.
Actual Behavior:

The addon works as intended, but the user is left confused by the lack of feedback about the underlying issue.
Suggested Improvement:

Add a clear warning when a naming conflict is detected, e.g.:

"Warning: Duplicate names detected. Blender may append .001 to resolve conflicts. Please rename conflicting objects to unique names before using this tool."

Source: Discord Feedback