fix: extend BaseKey to support number[] for UUID types

[Xenon010101]

• Extended BaseKey type from 'string | number' to 'string | number | number[]'
• Allows OpenAPI-generated types using number[] for UUIDs to work without type casting
• Added comprehensive tests for all BaseKey variants
• Resolves [BUG] BaseKey needs to support UUID #7403

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://refine.dev/docs/guides-concepts/contributing/#commit-convention

Bugs / Features

• Related issue(s) linked
• Tests for the changes have been added
• Docs have been added / updated
• Changesets have been added https://refine.dev/docs/guides-concepts/contributing/#creating-a-changeset

What is the current behavior?

What is the new behavior?

fixes (issue)

Notes for reviewers

[changeset-bot]

⚠️ No Changeset found

Latest commit: 55c7391

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[pcfreak30]

Thank you but https://github.com/Xenon010101/refine/blob/55c739158b98829fe6fad332ccb5aaac115585e1/packages/core/src/__tests__/basekey.test.ts this test file is honestly kind of useless as you aren't testing the types nor can you really. I would delete this, amend, and force push.