fix(composer): allow brick/math 1.0

[Spomky]

Problem

brick/math 1.0.0 was released on 2026-09-12. It is the first stable release and, according to its release notes, carries no change compared with 0.20.0. The constraint here stops at ^0.20, so any application that upgrades to brick/math 1.0 is blocked by this package until a release accepts it.

Change

^1.0 is added to the chain in composer.json and src/Library/composer.json, which must stay in sync.

-        "brick/math": "^0.12|^0.13|^0.14|^0.15|^0.16|^0.17|^0.18|^0.19|^0.20",
+        "brick/math": "^0.12|^0.13|^0.14|^0.15|^0.16|^0.17|^0.18|^0.19|^0.20|^1.0",

The explicit 0.x alternatives are kept: a 0.x minor may still break the API, so every one of them stays opted into deliberately. ^1.0 is a plain caret range because, from 1.0 on, brick/math follows semver and a minor is backward compatible.

Backward compatibility

Checked with composer/semver:

• Intervals::isSubsetOf(old, new) returns true, so no accepted version is lost
• the lower bound is unchanged at 0.12, nobody is forced to upgrade
• 1.x is accepted, 2.0 and above remain excluded

Verification

The test suite passes with brick/math 1.0.0 installed (891 tests, PHP 8.4). Because the released spomky-labs/pki-framework still caps brick/math at ^0.20, 1.0.0 was pinned with an inline alias (1.0.0 as 0.20.0) for the run; the tree will resolve 1.0.0 on its own once pki-framework ships its own constraint update.