v2 - refactor, fix bugs and support Backpack v7

[tabacitu]

WHY

BEFORE - What was wrong? What was happening before this PR?

Package was on v1.x supporting older PHP/Laravel/Backpack versions without comprehensive test coverage.

AFTER - What is happening after this PR?

v2.0 with modernized dependencies, automated testing, and improved API surface for extensibility.

HOW

How did you achieve that, in technical terms?

Foundation (PR #34):

• Complete package refactoring with comprehensive PHPUnit test suite
• Improved uploader architecture with better trait separation
• Added test models, migrations, and CI workflow

API improvements:

• Made strategy methods public (hasDeletedFiles(), shouldUploadFiles(), getEntryAttributeValue()) for extensibility
• Changed processRepeatableUploads() return type from array to Collection for consistency

Dependency updates:

{
  "require": {
    "backpack/crud": "^7.0",  // was ^6.x
    "spatie/laravel-medialibrary": "^10.7||^11.3"
  },
  "require-dev": {
    "phpunit/phpunit": "^11.0",  // was ^10.0|^11.0
    "orchestra/testbench": "^10.0",  // was ^8.0|^9.0|^10.0
    "spatie/laravel-translatable": "^6.0"  // new
  }
}

CI/CD:

• GitHub Actions workflow testing PHP 8.2-8.3 on push, PRs, and daily schedule

Is it a breaking change or non-breaking change?

Breaking changes:

• Requires PHP 8.2+ (dropped 8.1 and below)
• Requires Laravel 11+ (via Orchestra Testbench 10)
• Requires Backpack CRUD v7.0+
• processRepeatableUploads() returns Collection instead of array

How can we test the before & after?

Run test suite: composer test

Tests cover media uploads, collections, conversions, and repeatable fields across different uploader types.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

---

The next branch is where we bring together all fixes&features for our next version. This PR is here to document all PRs merged, all breaking changes, all remaining TODOs about this version until launch.

Features

??? made it work?!

Fixes

• [2.0] Refactoring, adding tests, cleanup #34 - what did [2.0] Refactoring, adding tests, cleanup #34 bring?

Breaking changes

• ??? - what did [2.0] Refactoring, adding tests, cleanup #34 bring?

Todos

Things to do before we merge this PR into main:

• fix tests not running on this branch
• adapt composer.json requirements to new version

[tabacitu]

@pxpm please help take this branch to a clean state:

• add a test workflow, so tests run on Github
• fill in my description above (in the first comment) so it's clear what this branch brings to the table

[tabacitu]

@copilot what does this PR do? What does it add or remove in terms of functionality? What does it change? Please provide a summary of what's different in this PR, because it's supposed to be a new version of this package and we want to let our users know what's different.

[Copilot]

@tabacitu I've opened a new pull request, #47, to work on those changes. Once the pull request is ready, I'll request review from you.