fix: Corrected ObjectToCamel, ObjectToPascal, ObjectToSnake types

[ryanhaugh]

There is an issue with the ObjectToCamel, ObjectToPascal, ObjectToSnake where they don't handle an array of string number unions correctly.

For example, the following:

ObjectToCamel<{
  prop_name: ("a" | "b" | "c")[];
}>

incorrectly returns:

{
    propName: "a"[] | "b"[] | "c"[];
}

when it should return:

{
    propName: ("a" | "b" | "c")[];
}

This PR fixes ObjectToCamel, ObjectToPascal, ObjectToSnake to return the correct string/number union array type.

[BigBallard]

Frankly, seeing fixes like this hang for months is discouraging when the library is as popular as it is.

[RossWilliams]

Frankly, seeing fixes like this hang for months is discouraging when the library is as popular as it is.

@BigBallard If you want to re-write the PR so it doesn't reformat all the lines then I will look at it.

[RossWilliams]

@ryanhaugh If you can preserve existing formatting then I can look at these changes.

[ryanhaugh]

@RossWilliams apologies for all the formatting changes - I've fixed them.

[ryanhaugh]

This PR also fixes this issue:

ObjectToCamel<{
  property_name: undefined;
}>;

incorrectly returns:

{
  propertyName: unknown[];
}

when it should return:

{
  propertyName: undefined;
}

@RossWilliams let me know if you need anything else from me so we can get this across the line - thanks!

[RossWilliams]

@ryanhaugh Build fails, you need to adjust the tests.

[ryanhaugh]

@RossWilliams I've simplified ObjectToCamel, ObjectToPascal, ObjectToSnake. I've also ensured all existing tests pass and have added more tests to ensure the bugs I've found are fixed with my PR.

[ryanhaugh]

@RossWilliams any chance you could take another look at this PR?
Thanks!
Ryan

[ryanhaugh]

@RossWilliams anything I can do to help move this along?

[ryanhaugh]

Starting to think this won't be reviewed - please prove me wrong.