docs(hierarchy): imports that still use an Asset's old names

[devGregA]

Description

Documents how DefectDojo Pro imports keep working after an Asset is moved or renamed, or an Organization is renamed, in docs/content/asset_modelling/PRO_hierarchy/reorganize_later.md (new section "Pipelines that still use the old names").

• Which imports resolve through a former name or Organization (import-scan, reimport-scan, SBOM import, API v3 import), and the name_resolution warning in the response.
• What stays the same: an unrelated Organization is still refused; former names expire after 180 days or when another Asset or Organization takes the name; a name two Assets shared resolves to neither; exact, case-sensitive matching; only a user who can view the Asset gets the resolution.
• Connectors, the Rules Engine, Smart Upload, cloud account onboarding and the GitLab project import also find renamed Assets, with the two safety exceptions.
• The Imports Follow Renames and Moves feature flag turns the behavior off.

English only. The Pro change is a private PR; merge the two together.

🤖 Generated with Claude Code