docs: anonymise project asset names in source comments

Measured figures are kept; only the studio-specific level and asset
names are generalised, and the Perforce rationale is reworded to
describe the class of setups rather than this one project.

Co-Authored-By: Claude Code <noreply@anthropic.com>

Source/AssetUsageAuditTests/Private/AssetUsageExporterLive.spec.cpp

@@ -176,7 +176,7 @@ BEGIN_DEFINE_SPEC(AssetUsageExporterLiveSpec,
     /**
      * The OFPA level with the fewest external actors.
      *
-     * Smallest on purpose: WP_Main owns roughly 16000 external packages and copying those in a test
+     * Smallest on purpose: WP_Example owns roughly 16000 external packages and copying those in a test
      * would move gigabytes. Search stops as soon as something small enough turns up.
      */
     static FName FindSmallestOfpaLevel(int32& OutExternalCount)
@@ -254,7 +254,7 @@ void AssetUsageExporterLiveSpec::Define()
 
         It("leaves the exported file writable even when the source is read-only", [this]()
         {
-            // This project is Perforce-primary, so unopened files are read-only on disk and Windows
+            // Perforce-primary projects keep unopened files read-only, so unopened files are read-only on disk and Windows
             // CopyFile carries the attribute across. A read-only export folder is useless to an
             // artist and breaks the exporter's own Overwrite policy on the next run.
             const FName Package = FindOrdinaryAssetPackage();