Let a select, a password and a file field span its container

<x-input>, <x-textarea> and <x-datepicker> took `full` to drop the 40rem
bound field.css puts on a text field from `medium`; <x-select>,
<x-password> and <x-file> did not, so a field inside a container that
already bounds it stopped short of that container's edge with no way to
say so. The three now take the prop and hand it to <x-field> like the
others. <x-choices> and <x-timepicker> still do not.

Found in SealShare: its share options, its admin settings and its user
settings are cards, and a card is exactly the "other container" M3 names
as the thing that should bound a field on a medium or expanded screen
instead of the 40rem ceiling.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

resources/views/components/file.blade.php

@@ -11,12 +11,13 @@
      it cannot be truncated or wrapped, and the caller shows what was chosen anyway, as previews. A
      screen reader still hears it. The errors are the model's and, for a `multiple` input, each
      file's (`photos.*`): a file refused for its size belongs under this field as much as the
-     batch's own count does. `label`, `hint`, `variant`; every other attribute reaches the `<input>`. --}}
+     batch's own count does. `label`, `hint`, `variant`; `full` takes the 40rem bound off a field its container already bounds. Every other attribute reaches the `<input>`. --}}
 
 @props([
     'label' => null,
     'hint' => null,
     'variant' => null,
+    'full' => false,
 ])
 
 @php
@@ -29,7 +30,7 @@
         : [];
 @endphp
 
-<x-livewire-material::field :$id :$label :$hint :$messages :$variant floated :class="$attributes->get('class')" :style="$attributes->get('style')" data-md-file>
+<x-livewire-material::field :$id :$label :$hint :$messages :$variant :$full floated :class="$attributes->get('class')" :style="$attributes->get('style')" data-md-file>
     <input
         {{ $attributes->except(['class', 'style', 'id', 'type']) }}
         type="file"