Fix SoundEvent name collisions by using InstanceID-based unique identifiers

[FRESH-SHIN]

Problem

Previously, SoundEvent identification relied solely on the asset's name. If multiple assets shared the same name—even if stored in different directories—it caused naming conflicts. Additionally, spaces in asset names led to registration and playback issues.

Solution

To ensure each SoundEvent has a unique identifier and to avoid whitespace-related issues, the naming convention has been updated in the following locations:

1. PHASESource.cs

   • When calling Helpers.PHASEPlaySoundEvent, the _soundEvent.name parameter has been replaced with "SoundEvent_" + _soundEvent.GetInstanceID().ToString().
   • This guarantees that each SoundEvent played by a PHASESource has a unique name at runtime.

2. PHASESoundEventNodeGraph.cs

   • The asset name used in Helpers.PHASERegisterSoundEventAsset has been updated to "SoundEvent_" + GetInstanceID().ToString(), ensuring that even if multiple assets have the same name or contain spaces, they will be uniquely registered.

Impact

• Prevents SoundEvent name collisions across different assets and directories.
• Avoids issues caused by whitespace in asset names.
• Ensures that every SoundEvent is uniquely identified during runtime.

Testing

• Created multiple SoundEvent assets with the same name but in different directories; they now register and play correctly without conflicts.
• Tested with asset names containing spaces; no longer triggers registration errors.

Additional Notes

• This change only affects internal SoundEvent naming and does not alter any user-facing functionality.
• All SoundEvents will now have a runtime-generated unique identifier, ensuring consistent behavior.