Super-Linter fails to lint PHP

[albertemozo]

Super-Linter works great for inspecting the template repo, but after you create a project from it and run it once, so you have the Composer files, it starts failing.

  2025-09-09 14:59:56 [INFO]   Found PHP files to validate. Check if we need to run composer install
  2025-09-09 14:59:56 [INFO]   Found Composer file: /github/workspace/composer.json
  2025-09-09 14:59:56 [FATAL]   Failed to run composer install for /github/workspace. Output: Installing dependencies from lock file (including require-dev)
  Verifying lock file contents can be installed on current platform.
  Your lock file does not contain a compatible set of packages. Please run composer update.
  
    Problem 1
      - Root composer.json requires php >=8.4.12 but your php version (8.4.11) does not satisfy that requirement.
    Problem 2
      - symfony/framework-bundle is locked to version v7.3.3 and an update of this package was not requested.
      - symfony/framework-bundle v7.3.3 requires ext-xml * -> it is missing from your system. Install or enable PHP's xml extension.
  
  To enable extensions, verify that they are enabled in your .ini files:
      - /etc/php84/php.ini
      - /etc/php84/conf.d/00_ctype.ini
      - /etc/php84/conf.d/00_curl.ini
      - /etc/php84/conf.d/00_dom.ini
      - /etc/php84/conf.d/00_iconv.ini
      - /etc/php84/conf.d/00_intl.ini
      - /etc/php84/conf.d/00_mbstring.ini
      - /etc/php84/conf.d/00_openssl.ini
      - /etc/php84/conf.d/00_simplexml.ini
      - /etc/php84/conf.d/00_tokenizer.ini
      - /etc/php84/conf.d/00_xmlwriter.ini
      - /etc/php84/conf.d/01_phar.ini
      - /etc/php84/conf.d/10_igbinary.ini
  You can also run `php --ini` in a terminal to see which files are used by PHP in CLI mode.
  Alternatively, you can run Composer with `--ignore-platform-req=ext-xml` to temporarily ignore these required extensions.
  Error: Your lock file does not contain a compatible set of packages. Please run composer update.

Currently, there's a PHP version mismatch and missing extensions.

Super-Linter doesn't provide an easy way to deal with this problem.

I'm planning to disable the PHP-related checks in Super-Linter and rely on the project containers to run that kind of checks, but for the sake of the developer experience this could be considered in the template, so users don't clash with these issues. Today it's PHP version and extensions, but generally speaking any kind of conflicts with Super-Linter can arise once the project is initialized.