Feature/export command documentation

[olarno]

I have created a command to retrieve all available commands within the project. After obtaining the list of commands and their respective names, I have included three key elements for each command:

• Description: A brief explanation of what the command does.
• Synopsis: Information on the available arguments or options for the command.
• Helper: Additional details and explanations about the command.

You can test this functionality by running the command using bin/console app:list-command. The resulting data can be found in the file tests/Command/result/defaultExport.json.

To begin testing, the objective is to:

• Execute the command.
• Compare the output of the command with the expected result. The two should match

Next step

• However, I've encountered an issue with this test: the expected result provided during testing does not match the actual output.
  • I need to investigate whether additional configurations or dependencies need to be loaded during the test to ensure both the expected result and actual output are consistent.
• I would also like to sync up with you to confirm the appropriate location for placing the code. Should it go into the framework_extra_bundle or another suitable location?

[mpoiriert]

@olarno I have review the PR, here are some other notes:

For phpcs and phpstan you can do:

Make linter

If you run all the test the ConsoleIntegrationTest should fail once you more the command in the proper namespace. Just fix it.

If you run the command in the test env it's normal that you don,t have the same list of command. Just focus on what the automation test output.

[olarno]

I applied your feedback, I struggle with the test 😓

1) App\Tests\Console\Command\ExportListCommandsCommandTest::testArguments
Error: Unknown named parameter $Path

/home/wwwroot/packages/tester/Application/CommandTestTrait.php:68