Summary of Changes

Enables use of snake_case style for custom fields (and rules and filters) in form XML by adding an additional class_exists() checks for entity types normalized to CamelCase. Currently, using snake_case is not possible unless a class alias is created through the class map.

With this PR, it will be possible to define a custom field class, for example, in pure CamelCase => ComplexTypeField and then use <field ... type"complex_type"/> to use it in the XML.

This change should be non-breaking as it only adds additional checks without altering existing code.

Testing Instructions

For custom fields with CamelClass compliant class names (like WorkflowComponentSections), you can replace their usage in forms with snake_case.

Actual result BEFORE applying this Pull Request

snake_case style in XML cannot be used for custom fields with CamelCase compliant class names.

Expected result AFTER applying this Pull Request

Using snake_case for custom fields like the WorkflowComponentSections should be possible. Existing forms should work as expected.

Documentation Changes Required

None I'm aware of.