Fix range filters, declare Laravel deps, add test suite and CI

[KalimeroMK]

Two bugs made the documented range filter a no-op

scopeFilter() matched the raw filter key against $fillable, so age_min / age_max were dropped
before reaching the range branch. The README's own example ($fillable = ['name','email','is_active']
with age_min/age_max filters) silently returned unfiltered results.

Working around it by adding age_min to $fillable hit a second bug: rtrim($field, '_min') strips a
character set, not a suffix.

tax_max     -> products.t          (expected products.tax)
domain_min  -> products.doma       (expected products.domain)
max_max     -> ''                  (empty column name)

Range keys now resolve via substr($field, 0, -4) and are matched against $fillable by their base column.

Also in this PR

• composer.json used Illuminate\* classes without requiring any Laravel package; added
  illuminate/database and illuminate/support (L10/11/12)
• removed the hardcoded "version": "1.0.0", which overrode the git tags on Packagist
• removed "minimum-stability": "dev" — it made composer install fail outright
• boolean fields are now table-qualified like every other condition (they were not, which breaks on joins)
• strict in_array() comparisons; declare(strict_types=1) and parameter/return types throughout
• whereLike splits on the last dot, so nested relations (posts.comments.body) work; it no longer
  re-registers if the macro already exists
• phpunit.xml rewritten for the PHPUnit 11 schema (verbose="true" was removed in PHPUnit 10)
• untracked .phpunit.result.cache and composer.lock
• GitHub Actions matrix: PHP 8.2/8.3/8.4 × Laravel 10/11/12, plus Rector

Tests

scopeFilter had no test at all. Added 12 covering exact, LIKE, boolean, whereIn, null handling,
non-fillable rejection, both range operators and the suffix-corruption cases; 7 for the macro including
nested relations. The 5 range tests fail on master and pass here.

19 tests, 20 assertions, green. Rector clean.

One behaviour change to be aware of

applyFieldFilter() is protected and its signature changed (it now takes the resolved column and
operator). Anything overriding it needs updating — unlikely, but it is the only BC-sensitive edit.