Enhance bindings of deep resource duplication

[RandomShaper]

Two changes:

1. Variant.duplicate_deep() argument is now told to be of the type enum::Resource.DeepDuplicateMode, instead of the wrong seemingly global enum::Resource.DeepDuplicateMode. See the excerpt below.
2. A few renames are made in the bindings, to remove the redundant 'resource' word. This is why I marked this PR as compat breaking. However, let's bear in mind this is compat breakage compared to prev 4.5 releases. Renames are these:
   • Resource.ResourceDeepDuplicateMode -> Resource.DeepDuplicateMode
   • Resource.RESOURCE_DEEP_DUPLICATE_* -> Resource.DEEP_DUPLICATE_*

---

Now, Variang::deep_duplicate() looks like this in the API JSON:

{
	"name": "duplicate_deep",
	// [...]
	"arguments": [
		{
			"name": "deep_subresources_mode",
			"type": "enum::Resource.DeepDuplicateMode", // <-- This is the improvement.
			"default_value": "1"
		}
	]
}

Fixes #107138.

[AThousandShips]

Makes sense to me

[akien-mga]

Missing the end of this sentence.

Wouldn't it make sense to just duplicate (heh) this enum in Resource so it can be exposed normally, and just cast it to the Variant one where relevant?

[RandomShaper]

I guess so. On the one hand, this case is already very special (the enum is global in C++ but scoped to Resource for scripting), so a little bit of special binding code doesn't seem out of place and makes the "bridging" very explicit. Not having to repeat the enum with the RESOURCE_ prefixes removed is an upside as well. On the other hand, what you suggest is more similar to what is already happening with certain enums in core_bind.h. If you ask me, I'd take the opposite direction, that is, integrating those duplicates.

I don't really have a strong opinion beyond personal taste.

In the meantime, I've fixed the sentence.

[akien-mga]

Thanks!