fix(drizzle-orm): fix configuration validation correct property checks for schema and casing

[diegoazh]

🚨 Important❗️❗️❗️
Change Summary:
I fixed two typo bugs in the configuration validation logic where the 'schema' and 'casing' configuration properties were being incorrectly validated by checking the wrong property (data['logger'] instead of data['schema'] and data['casing']).

Why This Matters:

1. Schema Validation Fix:

   • Before: The code mistakenly checked typeof data['logger'] when validating the 'schema' property.
   • After: Correctly checks typeof data['schema'] to validate the schema configuration.

2. Casing Validation Fix:

   • Before: The code checked typeof data['logger'] when validating the 'casing' property.
   • After: Properly checks typeof data['casing'] to validate the casing configuration.

Impact:

• Ensures the configuration validator works as intended for schema and casing settings.
• Prevents false negatives/positives where valid configurations might have been rejected or invalid ones accepted due to incorrect property checks.

This change addresses a subtle but critical validation oversight, ensuring the configuration checker accurately reflects the intended structure of the configuration object. It improves code correctness and reliability for schema and casing configuration handling.

[extradosages]

Thanks for contributing!

Can explain more thoroughly what the problem was and how this set of changes fixes it? Without context this PR does not seem correct?

As a nitpick, I would also suggest cleaning up the PR title is-config -> isConfig functioin -> function.

[diegoazh]

…repeated logger key when accessing data

Thanks for contributing!

Can explain more thoroughly what the problem was and how this set of changes fixes it? Without context this PR does not seem correct?

As a nitpick, I would also suggest cleaning up the PR title is-config -> isConfig functioin -> function.

Hello, @extradosages, I updated the PR description to give more context about this fix.
I guessed that the fix was easy and easy to understand, but my bad.