Fix Diagnostic window.

[DenisPimenov]

Hi @hadashiA !
I have the problem described here #621. I've been looking at the logic for collecting diagnostics and was going to suggest the simple solution, to check the unique scopes with GameObject instanceId.
There is a small problem from using Lookup when building a window. For this I had to add an instanceId to the name of the scope to output to the window.

Also wanted to suggest to add cleaning the scopes from the diagnostics after Dispose/Destroy.

If you have any other suggestions I can fix this solution.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
vcontainer	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 29, 2024 10:51am

[hadashiA]

Thank you!

However, there was a slight point of concern.
I want the DiagnosticsContext to be able to collect information in a Unity-independent layer. So I don't want to rely too much on the concept of instanceId.
After all, I don't think I need to increase the argument for GetCollector, since the string will still be the key.

I will probably rework that after your commit.
Thanks a lot.