Add profiler autostart indicator to EditorRunBar

[Geometror]

Followup to #96759

Addresses concerns that making the autostart of profilers persistent between sessions could lead to unexpected performance issues if users forget it's enabled.

Adds a small indicator near the EditorRunBar which shows up when autostart is enabled for any profiler.
Hovering shows the tooltip below.
Clicking opens the debugger view of the bottom panel and selects the first profiler for which autostart is enabled.

[arkology]

Just some thoughts.
Maybe making this button yellow color is too much (may look like "something terrible happened, you forgot to turn off the kettle"😄). Maybe something more neutral? I mean, you enable autostart and will be always "warned" even if it is inside single session.
How about to show it only when launching project and running it? And with less "distractive" color. For not to warn but notify.

UPD 2025-03-19.
After using it for a while I thinks presence of such button is good overall as it allows to switch to active profiler really fast. But it takes some place at top bar and its color is still distracting.

[akien-mga]

Looks pretty good to me overall!

I agree it might seem too distracting in the long run though, especially if some users want to always profile and are fine with the performance impact. But I'm also fine test driving it as is and seeing if users ask for changes.

[FoxyFox909]

Just some thoughts. Maybe making this button yellow color is too much (may look like "something terrible happened, you forgot to turn off the kettle"😄). Maybe something more neutral? I mean, you enable autostart and will be always "warned" even if it is inside single session. How about to show it only when launching project and running it? And with less "distractive" color. For not to warn but notify.

Maybe a softer yellow sure, but I agree with yellow in general since yellow = warning, and red = error in Godot already, and I do feel that this is more a light warning than a notification.

[KoBeWi]

I see some hard-coded values for the tab indices and profiler names. Ideally the profilers should register themselves to avoid hard-coding them. This can be refactored later though.

[KoBeWi]

Not important, but it's better to use PackedStringArray or StringBuilder instead for building the tooltip.

[KoBeWi]

The implementation is ok, though as I mentioned, the hard-coding should be eventually removed.

[Geometror]

Regarding the button's color and style: Initially, I went with a yellow icon and a flat button, but it looked off and wasn’t noticeable, so I inversed it. I realize this might feel a bit bold to some, but it provides a clear visual cue that your brain associates with "profiling mode." This can also work in reverse - you quickly notice when the indicator is absent, helping you spot when autostart isn't active but wanted. As for the color, if you can give me some suggestions I can try those, but IMO the default-warning-yellow works quite well here.

@KoBeWi I forgot to add a note on the hardcoded values :) Yep, that felt horrible, but I fear it's currently the only way to achieve this. (however, I've added this to my profiler refactoring list)

[akien-mga]

Needs rebase.

[Geometror]

Rebased.

[Repiteo]

Thanks!