Add mago formatter recipe

[Zuruuh]

Q	A
License	MIT
Packagist	https://packagist.org/packages/carthage-software/mago

[github-actions]

Thanks for the PR 😍

How to test these changes in your application

1. Define the SYMFONY_ENDPOINT environment variable:

   # On Unix-like (BSD, Linux and macOS)
   export SYMFONY_ENDPOINT=https://raw.githubusercontent.com/symfony/recipes-contrib/flex/pull-1811/index.json
   # On Windows
   SET SYMFONY_ENDPOINT=https://raw.githubusercontent.com/symfony/recipes-contrib/flex/pull-1811/index.json

2. Install the package(s) related to this recipe:

   composer req symfony/flex
   composer req 'carthage-software/mago:^1.0'

3. Don't forget to unset the SYMFONY_ENDPOINT environment variable when done:

   # On Unix-like (BSD, Linux and macOS)
   unset SYMFONY_ENDPOINT
   # On Windows
   SET SYMFONY_ENDPOINT=

Diff between recipe versions

In order to help with the review stage, I'm in charge of computing the diff between the various versions of patched recipes.
I'm going keep this comment up to date with any updates of the attached patch.

[Zuruuh]

The pipeline is failling because it doesn't support installing composer plugins 🤔 In theory mago could in fact setup it's own config by itself upon installation but I still think using flex here could help to maintain a config with sensible defaults and continue providing upgrades as the configuration's schema changes.

[diimpp]

@azjezz Hi, could you please review if this recipe aligns with https://github.com/carthage-software/mago generic configuration for symfony project.

Personally, I would like for format section to be removed, symfony plugin enabled, bin path removed and php_version somehow resolved at runtime and specified dynamically.

[Zuruuh]

The format section is exactly the default generated by the command mago init. For the linter section I commented it because it would raise warnings on a default symfony skeleton app 👍 (But yeah we could enable it)

[fabpot]

@Zuruuh What's the status of this PR?

[Zuruuh]

@fabpot I've just updated the pr to work with mago v1.0 👍 The CI is still failling because the composer package is a plugin and should be explicitely disabled in CI. Would it be fine if I do a followup pr to do it in the main symfony/recipes's github action ? (Since they share the same CI)