fix(security): gate AI tools by user ability and block admin-URL SSRF

The AI chat assistant scoped tool queries by company but ignored the
per-user Bouncer abilities the rest of the app enforces, so any `use ai`
holder could read customers, invoices, payments, and company financials
their role couldn't otherwise see. Each AiTool now declares a required
ability (entity-aligned); the registry hides unauthorized tools from the
model and refuses to execute them as a backstop.

Separately, admin/owner-supplied URLs were fetched server-side with no
guard against private/reserved targets (SSRF): the AI base URL, the
CurrencyConverter "DEDICATED" exchange-rate URL, and S3/Spaces file-disk
endpoints. A shared PrivateNetworkGuard now backs a PublicHttpUrl
validation rule (save-time) and runtime guards in each driver.

- AiTool::requiredAbility() + mapping across all 12 tools
- AiToolRegistry filters schemas() by ability and re-checks in execute()
- PrivateNetworkGuard / BlockedUrlException / PublicHttpUrl rule (new)
- Rule wired into AI config (service + 3 controllers), exchange-rate,
  and file-disk endpoints; runtime guards in OpenRouterDriver,
  CurrencyConverterDriver, and FileDiskService
- Tests for ability filtering, the guard, the rule, and 422 rejections

app/Http/Controllers/Admin/Settings/AiConfigurationController.php

@@ -3,6 +3,7 @@
 namespace App\Http\Controllers\Admin\Settings;
 
 use App\Http\Controllers\Controller;
+use App\Rules\PublicHttpUrl;
 use App\Services\AiConfigurationService;
 use App\Support\Ai\AiDriverFactory;
 use App\Support\Ai\AiException;
@@ -86,7 +87,7 @@ class AiConfigurationController extends Controller
         $this->validate($request, [
             'ai_driver' => 'required|string',
             'ai_api_key' => 'nullable|string',
-            'ai_base_url' => 'nullable|string|url',
+            'ai_base_url' => ['nullable', 'string', 'url', new PublicHttpUrl],
         ]);
 
         // If the masked placeholder was submitted, fall back to the stored key