Add command to dump required PHP extensions based on vendor/composer/…

[CyberLine]

…installed.json, composer.lock, composer.json (in this order)

What does this PR do?

This fixes #338

[crazywhalecc]

1. To be accurate, it seems we can only determine which extensions are needed from both installed.json and composer.json. If these two files do not exist in current or passed directory, it will fail directly. What do you think?
2. I think we can add some project parameters, as well as remove redundant output, optional extension validation using spc config, so that static-php-cli can use the output directly. (Don't worry, I have already written some of the functionality, but I still need to figure out the first problem)

[CyberLine]

1. To be accurate, it seems we can only determine which extensions are needed from both installed.json and composer.json. If these two files do not exist in current or passed directory, it will fail directly. What do you think?

The most accurate result is given, if you have all 3 files exist. Maybe i can add an error if composer install was not run in before (so installed.json is not present) or at least composer.lock must be present.

2. I think we can add some project parameters, as well as remove redundant output, optional extension validation using spc config, so that static-php-cli can use the output directly. (Don't worry, I have already written some of the functionality, but I still need to figure out the first problem)

I've just created the logic to get all extensions from all possible files. Gimme some more informations on what your goal is and i will change it.

[crazywhalecc]

I mainly separated files to parse and add some options, and if you think there's anything that needs improvement, feel free to suggest it.

[CyberLine]

Looks fine and works for me. Maybe we can add --for-extensions=auto which then internally calls this command?

[crazywhalecc]

Looks fine and works for me. Maybe we can add --for-extensions=auto which then internally calls this command?

It is possible to implement internal calls, but --for-extensions=auto may not be appropriate because there are cases where the project path is not the current working directory. We need a way to pass in the path.

I am not very good at parameter naming and design, especially in mixed parameter situations (sometimes I need to merge the list of extensions exported in the project and the list of extensions specified via the command line).

[CyberLine]

We also need to add back composer.json to the list of parsed files. Why? Because if i have custom extension requirements in my project, they will only be found in composer.json, not reflected in composer.lock

[crazywhalecc]

they will only be found in composer.json, not reflected in composer.lock

@CyberLine It can be found in platform segment:

{
    "platform": {
        "php": ">= 8.1",
        "ext-mbstring": "*",
        "ext-zlib": "*"
    }
}