Fix: Correctly sort composer-plugin-api

[localheinz]

This pull request

• asserts that composer-plugin-api is correctly sorted

Related to ergebnis/composer-normalize#673.

[codecov]

Codecov Report

Merging #463 (0923d66) into main (e1d2c72) will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff             @@
##                main      #463   +/-   ##
===========================================
  Coverage     100.00%   100.00%           
  Complexity       164       164           
===========================================
  Files             34        34           
  Lines            515       515           
===========================================
  Hits             515       515           

Impacted Files	Coverage Δ	Complexity Δ
src/Vendor/Composer/PackageHashNormalizer.php	100.00% <ø> (ø)	7.00 <0.00> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e1d2c72...0e5baab. Read the comment docs.

[rjgwiz]

This is still an issue for me.

composer.json:

    "require": {
        "php": ">=7.4",
        "composer-plugin-api": "^2.0",
        "acquia/blt": "^13",

command line outputs:

composer --version
Composer 2.3.1 2022-03-30 15:41:28
...
 - ergebnis/composer-normalize installed in version 2.25.1
...

$ composer validate
./composer.json is valid, but with a few warnings
See https://getcomposer.org/doc/04-schema.md for details on the schema
# General warnings
- require.drupal/security_review : unbound version constraints (*) should be avoided
- require.drupal/view_custom_table : exact version constraints (9.0.x-dev@dev) should be avoided if the package follows semantic versioning
Links under require section are not sorted.
$ composer normalize
Running ergebnis/composer-normalize by Andreas Möller and contributors.

./composer.json is already normalized.

Composer validate and composer normalize keep conflicting each other on the sorting placement of composer-plugin-api. Did something in Composer v2 reintroduce this bug?