RedMser

I'm busy with work so @Yarwin is free to work on it if they want. But the issue should definitely be fixed to help readability of docs.

> It also makes me wonder whether all `_get_configuration_warnings()` methods (or at least the method bodies) should be placed behind `#ifdef TOOLS_ENABLED` to reduce binary size. I tried this change...

This PR should be ready now. I've rewritten the description, to remove finished TODOs and clarify what this PR exactly does. A larger UI change has been made by introducing...

Great idea, here's how it looks after said changes: 

> IMO the inspector warnings should be folded by default. Sure I can change that. > Also why are they clickable? Yeah I have a TODO to replace them with...

Thanks for the review KoBeWi, I did a first pass which includes all comments marked as resolved. It's a new commit so it's easier to go over just these changes....

OK new changes, as new commits to help make review easier. - Replaced ItemList with RichTextLabel for the UI. - Introduced `ConfigurationInfo` struct which is used everywhere internally, while the...

I've rebased to latest master and verified that everything still works. No problems when using the `template_release` either, `update_configuration_(info|warnings)` calls are a no-op as is intended. Not sure if there's...

> It could fallback to warning, but not sure about the error. It makes sense, but it's being spammed a lot. I changed that one to `ERR_PRINT_ONCE` but not sure...

> adding a deferred error print that can happen at most once per frame. Something like `queue_print_error`, with check for unique messages. I could try implementing this (maybe as a...