Enums collisions are not detected when validating schema with native enums

Describe the bug
When using native enums, as showcased here https://lighthouse-php.com/master/the-basics/types.html#native-php-definition coupled with https://github.com/BenSampo/laravel-enum
Enum name collisions are not detected when running php artisan lighthouse:validate-schema

Expected behavior/Solution
Validating schema should detect enum name collisions when using native php enums

Steps to reproduce

1. install https://github.com/BenSampo/laravel-enum
2. create a new enum MyEnum.php

<?php

declare(strict_types=1);

namespace App\Enums;

use BenSampo\Enum\Enum;

class MyEnum extends Enum
{
    public const DONE = 'DONE';
}   

3. create a new graphql enum with the same name

enum MyEnum {
    DONE
}

4. run php artisan lighthouse:validate-schema
5. Output is The defined schema is valid.
   Output/Logs

# Add in log output/error messages here

Lighthouse Version
4.18.0

Reproduce the issue using the native enum example and the php artisan lighthouse:validate-schema command, then trace how native PHP enums and GraphQL enums are loaded during schema validation. Compare the native-enum path with collision detection for regular GraphQL enums. Done means the command reports a collision for the duplicated MyEnum name.