[Taldres]

Apps that model their environments as an enum can already use it with the #[Bind] attribute, but not with the framework's other environment checks:

enum Environment: string
{
    case Local = 'local';
    case Staging = 'staging';
    case Production = 'production';
}

App::environment(Environment::Production);
// Error: Object of class Environment could not be converted to string

Schedule::command('reports:send')->daily()->environments(Environment::Production);
// No error, but the task never runs

The scheduler case is the more surprising one. environments() stores the enum as-is, and runsInEnvironment() compares it against the current environment string, so the task is silently skipped on every environment.

This PR passes the given values through enum_value(), the same way #[Bind] already handles its environments argument. Backed enums (and unit enums, by case name) now work with:

• App::environment() / app()->environment(), including @env(...) in Blade, which compiles down to it
• environments() on scheduled events and on Schedule::environments(...)->group(...)

String values behave exactly as before, wildcard patterns included, and signatures and return types are unchanged. The scheduler stores the normalized strings, so anything reading $event->environments, like schedule:list --json, still gets plain strings.

Tests cover both the application and the scheduler.