Add a warning when running itest through the editor.

[mhoff12358]

They need to be run through an exported binary, so print a readable warning and don't try to run the tests if someone (like me) does try.

[GodotRust]

API docs are being generated and will be shortly available at: https://godot-rust.github.io/docs/gdext/pr-412

[mhoff12358]

@Bromeon This seems to fail CI because the CI is running it through the editor, just in a different way. Dang.

[Bromeon]

I think has_feature("editor") is the wrong check; it checks whether the Godot binary is an editor build. See also Godot docs, although they're not very expressive here.

I'm not sure if this is even possible -- but since you experience a crash when launching from editor but not when from command line, there must be some sort of observable behavior that differs. I just don't know whether there's an API...

[Bromeon]

@mhoff12358 Any updates on this one?

[StatisMike]

I wonder if reverse approach can be sensible:

I presume we are talking about running tests with check.sh as credible way. Maybe we could pass an environment variable in the command line there, which could be checked by TestRunner. If the environment variable is set to correct value, tests would go as expected. If not - then issue the error.

[Bromeon]

I found a better option: check whether editor is running (dynamically, not via feature) and if we are in headless mode.

Changed the commit accordingly. Thanks for this addition and the input!