Enum naming strategy should allow different naming conventions used in source code

### Is your feature request related to a problem? Please describe.

Currently `CamelCaseStrategy` in `EnumNamingStrategies` assumes that enum entries in source code are named using `UPPER_SNAKE_CASE` convention, for example: `enum Size { VERY_BIG }`.
However in Kotlin quite often `UpperCamelCase` is used, for example `enum class Size { VeryBig }`. `CamelCaseStrategy` in `EnumNamingStrategies` does not work with such a naming.

### Describe the solution you'd like

Strategies in `EnumNamingStrategies` should work with enum entries written in code using different naming conventions like `UpperCamelCase`.

### Usage example

_No response_

### Additional context

_No response_