fix(blob): pass R2 jurisdiction to generated wrangler bindings (#908)

[blue-rigel]

Summary

Fixes #908 by passing hub.blob.jurisdiction through to the auto-generated Cloudflare R2 wrangler binding.

Jurisdictional R2 buckets (e.g. EU) require jurisdiction on the r2_buckets entry. NuxtHub previously only mapped binding and bucket_name, so those buckets could not be configured via hub.blob alone.

Example

export default defineNuxtConfig({
  hub: {
    blob: {
      driver: 'cloudflare-r2',
      bucketName: 'my-eu-bucket',
      jurisdiction: 'eu'
    }
  }
})

Generates:

{
  "r2_buckets": [
    {
      "binding": "BLOB",
      "bucket_name": "my-eu-bucket",
      "jurisdiction": "eu"
    }
  ]
}

When jurisdiction is omitted, the binding is unchanged (no extra field).

Changes

• Pass optional jurisdiction in src/blob/setup.ts when generating the R2 wrangler binding
• Add jurisdiction?: string to CloudflareR2BlobConfig and exclude it from runtime driver options
• Document the option in blob and deploy docs
• Tests: omit when unset; include when set (eu)

Test plan

• pnpm test test/wrangler.test.ts test/wrangler-jurisdiction.test.ts
• Configure hub.blob with jurisdiction: 'eu' and confirm .output/server/wrangler.json (or nitro wrangler config) includes it
• Configure without jurisdiction and confirm the field is absent

[vercel]

@blue-rigel is attempting to deploy a commit to the NuxtLabs Team on Vercel.

A member of the Team first needs to authorize it.