[11.x] Add BackedEnum support to Gate methods

[diaafares]

Hi,
Using Enums enhances code readability and reduces typos; it also improves IDE support by providing better autocomplete

This change is backward compatible and shouldn't bring any breaking changes.

enum Abilities: string {
    case VIEW_DASHBOARD = 'view-dashboard';
    case EDIT = 'edit';
    case UPDATE = 'update';
}


// Before
Gate::define('view-dashboard', function (User $user) {
    return $user->isAdmin;
});

Gate::authorize('view-dashboard');
Gate::inspect('view-dashboard');
Gate::check('view-dashboard');
Gate::any(['edit', 'update], $post);
Gate::none(['edit', 'update]], $post);
Gate::allows('update', $post)
Gate::denies('update', $post)

// After
Gate::define(Abilities::VIEW_DASHBOARD, function (User $user) {
    return $user->isAdmin;
});

Gate::authorize(Abilities::VIEW_DASHBOARD);
Gate::inspect(Abilities::VIEW_DASHBOARD);
Gate::check(Abilities::VIEW_DASHBOARD);
Gate::any([Abilities::EDIT, Abilities::UPDATE], $post);
Gate::none([Abilities::EDIT, Abilities::UPDATE], $post);
Gate::allows(Abilities::UPDATE, $post)
Gate::denies(Abilities::UPDATE, $post)

[iBotPeaches]

@diaafares - once these 2 (#52677, #52679) got merged together they led to build failures due to the enum collide of

enum AbilitiesEnum: string {
    case VIEW_DASHBOARD

[diaafares]

@iBotPeaches I added a new PR to fix the issue
#52683
Can you please check it to see if it solves the problem?