Description

ExtraPropertyDefinition types its $defaultValue as int|float|string|bool|null (docblock @param scalar|null), and the repository already casts the raw DB string back to that declared type via ExtraPropertyValueCaster::castFromDb(). But the CQRS layer narrowed the same value to ?string:

• AddExtraPropertyDefinitionCommand::$defaultValue was ?string, so a non-string scalar passed programmatically (e.g. an integer default coming from the Admin API JSON payload) raised a TypeError under declare(strict_types=1).
• EditableExtraPropertyDefinition::$defaultValue was ?string, and GetExtraPropertyDefinitionForEditingHandler forced a (string) cast when building it — losing the scalar type carried by the entity.

This PR aligns the CQRS layer with the entity:

• Widen $defaultValue (constructor param + getter) to int|float|string|bool|null in AddExtraPropertyDefinitionCommand and EditableExtraPropertyDefinition.
• Drop the lossy (string) cast in GetExtraPropertyDefinitionForEditingHandler so the edit DTO carries the real scalar.
• Move that (string) cast to ExtraPropertyDefinitionFormDataProvider, where the back-office TextType field needs a string for display. The rendered form value is therefore unchanged — the cast simply happens at the form boundary instead of inside the query handler.

No BC break: string defaults continue to work everywhere (string is part of the widened union), and the only in-repo command caller (the BO form data handler) still passes a string.

How to test

Unit tests cover the type-preservation contract on both CQRS classes:

vendor/bin/phpunit -c tests/Unit/phpunit.xml \
  tests/Unit/Core/Domain/ExtraProperty/Command/AddExtraPropertyDefinitionCommandTest.php \
  tests/Unit/Core/Domain/ExtraProperty/QueryResult/EditableExtraPropertyDefinitionTest.php

Each test constructs the class with int, float, bool, string and null defaults and asserts (assertSame) that the getter returns the same typed value.

Test verification (RED → GREEN)

RED — new tests on develop (before the production change): the int/float/bool data sets fail because the constructor still declares ?string:

TypeError: AddExtraPropertyDefinitionCommand::__construct(): Argument #10 ($defaultValue)
must be of type ?string, int given
TypeError: EditableExtraPropertyDefinition::__construct(): Argument #10 ($defaultValue)
must be of type ?string, float given
...
Tests: 12, Assertions: 4, Errors: 8.

GREEN — after widening the types (full ExtraProperty unit suites, includes the 12 new cases):

PHPUnit 10.5.63
Tests: 491, Assertions: 1356.
OK

php-cs-fixer (dry-run) and phpstan on the changed files both report no errors.