Make "IdSistemaInformatico" configurable to support multiple test instances

[ilie]

Summary

• Made IdSistemaInformatico configurable via VERIFACTU_SYSTEM_ID environment variable
• Removed hardcoded value from AeatClient to prevent AEAT test rejections

Problem

While testing I would clear the database multiple times and reseed it back tih this command: php artisan migrate:fresh -- seed.
AEAT pre-production environment is so strict that it will reject the same invoice twice, or even create a new invoicing serie and tried again while testing, AEAT would reject invoices with the error that the same invoice with the same NIF cannot be
declared as the first invoice when using the same NIF and IdSistemaInformatico. This prevented testing.

Solution

• Added system_id configuration in config/verifactu.php with default value '01'
• Updated AeatClient.php to read from config instead of hardcoded value
• Allows different test instances to use different system IDs via environment variables

Benefits

• It allows you to have multiple invoicing systems using LaravelVeriFactu package that are independent on eachother.

Changes

• config/verifactu.php: Added system_id config key
• src/Services/AeatClient.php:261: Changed hardcoded '01' to config('verifactu.system_id', '01')

Test plan

• Set different VERIFACTU_SYSTEM_ID values in different environments
• Verify AEAT accepts first invoices from each unique system ID
• Confirm default value '01' is used when environment variable is not set

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud