Document how to use memory profiling

[alice-i-cecile]

          Not going to block on it, but we should have something for how to use the feature in `profiling.md`.

Originally posted by @hymm in #8272 (review)

We should also encourage users to keep this off when profiling except when explicitly needed due to the high overhead.

[Mohamed-khattab]

hello @alice-i-cecile ,

I am interested in contributing to the Beavy project on GitHub.
As a new contributor, I would like to work on resolving this issue by creating the requested document. I believe that this will be a great opportunity for me to learn more about open source development and contribute to the project.

Before I proceed, I would like to confirm with you if the issue is still open and available for contributions. Additionally, I would appreciate any suggestions or feedback you may have to help me get started with creating the document.

[alice-i-cecile]

Great :) This is still available.

In order to turn this on, you need to enable the cargo feature added here when running your app.

This is the file we should be modifying: https://github.com/bevyengine/bevy/blob/main/docs/profiling.md :) Try your best to get tracy set up on your PC so you can test that the instructions work too! If you get stuck in the install process, post a new Discussion here for troubleshooting help so others can Google errors you run into in the future.

[theotherphil]

@mockersf I've just tried using your Tracy memory profiling feature on a MacBook in order to update the docs for this issue.

When trying it out, the Zone Info tab in Tracy shows something similar to your PR:

However, the Memory tab is missing function names for the call stacks:

(Screenshots unhelpfully and somewhat irrationally truncated to not include my full name.)

Is this something that you would expect to work, or should I add a note in the docs that this isn't supported?

[mockersf]

probably not supported for now!