Field names overriding with graphql-default always force case format

### Version Information

Server Version: 2.15.0
CLI Version (for CLI related issue): 2.15.0

### Environment

OSS

### What is the current behaviour?

When you run the engine with the graphql-default naming convention if you override a field name it will be automatically transformed in snakeCase

### What is the expected behaviour?

An onverrided field name should not be touched

### How to reproduce the issue?

1. start the engine with the graphql-default naming convention
2. create a table
3. create a field called my_field
4. override its name to my_field
5. go in the API view and check the field name. It will be myField instead of the overridden value

### Screenshots or Screencast


### Please provide any traces or logs that could help here.

### Any possible solutions/workarounds you're aware of?

### Keywords
naming convention override field name case

Reproduce the behavior using the graphql-default naming convention, an overridden field name, and the API view described in the issue. Trace the naming-convention handling from that reproduction and verify that the API preserves the explicitly overridden field name rather than converting it to camelCase.

Written by the indexing model from the issue text.