Add Tinker MCP tool (opt-in via config)

[pushpak1300]

Currently the tinker MCP tool is gone (removed in #629), so agents have to use php artisan tinker --execute '...' via shell. That round-trips through shell escaping and bites pretty consistently. As #667 points out, agents tend to fail 2-3 times on quoting before they get a snippet right.

This PR brings the tool back, but opt-in so it stays off by default. Flip it on with:

```php
// config/boost.php
'tinker_tool_enabled' => true,
```

core.blade.php swaps the guidance to prefer the MCP tool when the flag is on, and keeps the existing --execute instructions otherwise.
Closes #667.

[TonsiTT]

Thanks. Going to switch to this branch.
To show how much it sucked, here is a example of codex trying to use Tinker Tool. It tried 11 times and failed each time and it literally ended up encoding the whole code block to base64 and running it via decode on Tinker as it couldn't figure out how to use the cli version with normal code block due to formatting issue

Ran 11 commands, used Laravel Boost
Ran php artisan tinker
The interactive Tinker paste split the closure at a ternary line, so that attempt didn’t run the validation loop. I’m switching to a single --execute eval(base64_decode(...)) payload so the same app-context code runs as one PHP block.
Ran 2 commands
Ran base64 -w0 <<'PHP' $categor....
Ran php artisan tinker --execute='eval(base64_decode("JGNhdGVnb3J5S.......=="));

[pushpak1300]

which model are you using ? @TonsiTT

[rforced]

@pushpak1300 where does that configuration go in boost.php?

'tinker_tool_enabled' => true,

Is it nested under another key?

[pushpak1300]

nope @rforced

[rforced]

@pushpak1300 can you comment on why the setting isn't nested under the MCP settings? Right now we have this. Having this setting at top level is starting to make boost's configuration feel very inconsistent

    'mcp' => [
        'tools' => [
            'exclude' => [
                GetAbsoluteUrl::class,
            ],
        ],
    ],

[pushpak1300]

both can work. this is experimental feature. so i haven't documented anything.

[rforced]

I understand, thank you