Permit to Inject GlpiAsset

[tsmr]

Checklist before requesting a review

Please delete options that are not relevant.

• [X ] I have performed a self-review of my code.
• I have added tests (when available) that prove my fix is effective or that my feature works.
• I have updated the CHANGELOG with a short functional description of the fix or new feature.
• This change requires a documentation update.

Description

Permit to Inject GlpiAsset (and add Injectable Capacity)
Warning this development d'ont add type & model injection of GlpiAsset

[Herafia]

Hello @tsmr,
You can use these commands to resolve the CI issue:
../../vendor/bin/phpstan
../../vendor/bin/php-cs-fixer fix
../../vendor/bin/rector
php bin/console tools:licence_headers_check

Thank you!
Laura - Teclib

[Rom1-B]

No test (unit or functional) validates that a GlpiAsset custom asset definition can actually be injected end-to-end. Given the size of the change (492 lines, dynamic eval()-based class generation, a new capacity with register/unregister lifecycle), and that the plugin already has unit tests for comparable injection classes (tests/unit/GroupInjectionTest.php, tests/unit/CommonInjectionLibDataAlreadyInDbTest.php), a test is both feasible and needed here. Can you add a unit or functional test that enables IsInjectableCapacity on an asset definition, injects a row through the generated AssetInjection subclass, and asserts the resulting asset item?