Add bulk actions (attach, detach, manage) to Spatie Laravel Tags Plugin

[intrepidws]

Description

This PR adds table bulk actions to the filament/spatie-laravel-tags-plugin package. Until now the plugin shipped a form field (SpatieTagsInput), a table column (SpatieTagsColumn), and an infolist entry (SpatieTagsEntry), but there was no way to tag many records at once. These actions fill that gap, mirroring the behavior and options of the existing SpatieTagsInput.

Three new bulk actions are added:

• AttachSpatieTagsBulkAction — opens a modal with a tags input and attaches the chosen tags to every selected record. Existing tags on a record are preserved (via syncWithoutDetaching), and tags that don't exist yet are created.
• DetachSpatieTagsBulkAction — removes the chosen tags from the selected records without deleting the tags themselves from the database.
• ManageSpatieTagsBulkAction — a single modal with two tags inputs, so users can attach some tags and detach others in one pass. Each record's attach + detach is wrapped in a DB::transaction so a mid-record failure can't leave it half-updated.

use Filament\Actions\AttachSpatieTagsBulkAction;
use Filament\Actions\DetachSpatieTagsBulkAction;
use Filament\Actions\ManageSpatieTagsBulkAction;
use Filament\Tables\Table;

public function table(Table $table): Table
{
    return $table
        ->toolbarActions([
            AttachSpatieTagsBulkAction::make(),
            DetachSpatieTagsBulkAction::make(),
            // ...or, instead of the two above:
            ManageSpatieTagsBulkAction::make(),
        ]);
}

Visual changes

Functional changes

• Code style has been fixed by running the composer cs command.
• Changes have been tested to not break existing functionality.
• Documentation is up-to-date.

[danharrin]

Thanks for you work here, I think I am going to pass though. In my opinion customisability is quite important for tagging UIs as tags can be used in a variety of ways, and I think having users define these in their apps is probably not too bad. I would suggest opening discussion threads in the future and tagging me to suggest big features like this as it helps us validate it first before you spend time on the implementation.