Register enum type names in release build

[heppocogne]

This commit fixes #64084

• Add script error for non-existing C++ enum types.
• Modify macro definitions for release build.

[anvilfolk]

Can you fix the conflicts? I think this is the only way to fix #69532 :)

[heppocogne]

@anvilfolk
Fixed confliction.

[anvilfolk]

Thank you! You also need to squash your commits into a single commit! :)

[heppocogne]

ok, I squashed 2 commits into a commit.

[anvilfolk]

Perfect! I struggled a lot to make that work the first time! :) Let's see if we can't get this PR in :)

[akien-mga]

You still have two commits, because you merged the master branch back on top of your squashed commit instead of rebasing:

Moreover, the commit message should not be "Squash commit" - that's what you did, but we need to know what the commit does. It should describe how it improves/changes/fixes engine functionality. See https://github.com/godotengine/godot/blob/master/CONTRIBUTING.md#format-your-commit-messages-with-readability-in-mind

[anvilfolk]

Sorry, my bad for not spotting that. That's what you get with insomnia at 5am ;)

This guide helped me: https://www.sitepoint.com/git-interactive-rebase-guide/

[heppocogne]

@akien-mga @anvilfolk
Thanks for your help. I could squash all commits into one commit.

[vnen]

I've actually been meaning to do this, since the alternative is remove the ability to address enums by their names. The only thing I want to see is a comparison in size of release builds with and without this. Though I doubt it would be much since I don't think that are that many enums around.

[vnen]

Given this is the same with or without DEBUG_METHODS_ENABLED it could stay outside the #ifdef too.

[heppocogne]

Sorry, that's probably because I made mistakes when I tried to fix conflicts.
And unfortunately, my branch seems to be broken now (cannot checkout or reset). I will close this PR and make new one later if necessary.

[YuriSizov]

Hey, @heppocogne, you need to rebase and squash again. You seem to have dragged unrelated changes into your PR, probably by merging master into it. Remember that in feature branches you shouldn't merge master, you should rebase those branches against the master instead.

[heppocogne]

@YuriSizov Thank you! I could manage to restore my repository.

[vnen]

@neikeq yeah, it would be interesting to profile that, maybe we can optimize it. That could potentially help with editor startup as well.

[vnen]

Would be interesting to profile startup to see the actual impact, but I believe this change is needed in any case to keep consistency between debug and release behavior.

[akien-mga]

Thanks!

[neikeq]

If this has a negative on startup time, perhaps we could cache the result from enum_qualified_name_to_class_info_name into a static field. The downside of being static is that it's kept alive until the program finishes, but honestly, adding it to ClassDB is almost the same in practice.