chore: Bisect should use CacheClearCommand in core instead

[datlechin]

Currently, the Flarum framework (https://github.com/flarum/framework/blob/2.x/framework/core/src/Extension/Bisect.php#L35) uses the Composer\Command\ClearCacheCommand class, but the core composer.json does not require the composer/composer package. This causes an error when running the php flarum command.

To resolve this, there are two possible approaches:

1. Move the composer/composer package to the core and remove it from the extension-manager.
2. Create a new command in the core to handle clearing the Composer cache by forking the necessary code from the composer/composer package.

In this PR, I've opted for the first solution by moving the composer/composer package to the core composer.json and removing it from the extension-manager.

Fixes #0000

Changes proposed in this pull request:

Reviewers should focus on:

Screenshot

QA

Necessity

• Has the problem that is being solved here been clearly explained?
• If applicable, have various options for solving this problem been considered?
• For core PRs, does this need to be in core, or could it be in an extension?
• Are we willing to maintain this for years / potentially forever?

Confirmed

• Frontend changes: tested on a local Flarum installation.
• Backend changes: tests are green (run composer test).
• Core developer confirmed locally this works as intended.
• Tests have been added, or are not appropriate here.

Required changes:

• Related documentation PR: (Remove if irrelevant)
• Related core extension PRs: (Remove if irrelevant)

[SychO9]

Thanks for the PR!

The mistake is actually that the bisect class should be using the core CleaeCacheCommand instead. We would definitely not want to require composer in core otherwise.

Could you please make that change?