BulkActions - Migration to AlpineJS v2

[lrljoe]

How this works

Changes to a number of blades, and a couple of traits have occurred to allow for this to work smoothly.

The design is so that the "Selected" is only updated on a typical Livewire refresh, rather than forcing it on each checkbox select.

Setup

• In wrapper.blade.php, a number of AlpineJS variables are set.
  • selectedCount (integer - used while on the same page to avoid a Livewire refresh)
  • visibleItems (array - stores a list of Visible Items)
  • selectedItems (entangled - stores a list of Selected Items, is a deferred entanglement)
  • allItemsSelected (boolean - returns if all items are selected or not)
  • selectAllOnPage() (function - selects all items on a page)

When Checking a Box

• The value of the checkbox is set to the Primary Key of the row, to ensure persistence
• selectedItems (AlpineJS) variable is updated, so it will be updated during the next Livewire lifecycle

When loading a new page

• The value of the checkbox is set to the Primary Key of the row, to ensure persistence
• The checkbox for each row is bound to selectedItems, so it will display the correct state when browsing between pages.

All Submissions:

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

New Feature Submissions:

1. Does your submission pass tests and did you add any new tests needed for your feature?
2. Did you update all templates (if applicable)?
3. Did you add the relevant documentation (if applicable)?
4. Did you test locally to make sure your feature works as intended?

Changes to Core Features:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you successfully ran tests with your changes locally?

[lrljoe]

@siebsie23 - This replaces the other PR, and I'd welcome any testing you do before it hits the next release, as you're clearly keen for this! :)

Keep in mind that this does use new functions from the develop branch, so you're best off using the develop branch to test.