Revert "Drop sub-component targets (#8966)"

[fendor]

This reverts commit 3f4c81f.

Please read Github PR Conventions and then fill in one of these two templates.

---

Template Β: This PR does not modify cabal behaviour (documentation, tests, refactoring, etc.)

Include the following checklist in your PR:

• Patches conform to the coding conventions.

Closes #9688

[fendor]

This does not need to be merged as is but serves as somewhat of a reminder :)

[andreabedini]

It's clear the ecosystem is put togheter with sticky tape

If this is the only option, I reckon it's a fair call to revert.

[Mikolaj]

For the record, this reverts #8966.

I agree it's unfortunate we have to revert this. Let's at least try to improve the API, docs, tests.

[Mikolaj]

A random CI infra failure: "Mikolaj token is invalid, make sure Mikolaj can still log in on the Mergify dashboard."

I will keep insisting.

[Mikolaj]

@mergify refresh

[mergify]

refresh

✅ Pull request refreshed

[Mikolaj]

@mergify unqueue

[mergify]

unqueue

☑️ The pull request is not queued

[Mikolaj]

@mergify queue

[mergify]

queue

🛑 The pull request has been removed from the queue default

The pull request can't be updated.

You can take a look at Queue: Embarked in merge queue check runs for more details.

In case of a failure due to a flaky test, you should first retrigger the CI.
Then, re-embark the pull request into the merge queue by posting the comment
@mergifyio refresh on the pull request.

[Mikolaj]

@mergify rebase

[mergify]

rebase

❌ Base branch update has failed

Mikolaj token is invalid, make sure Mikolaj can still log in on the Mergify dashboard.

[Mikolaj]

I'm able to rebase just fine in #9698, so may this be something wrong with the PR? I can see "Maintainers are allowed to edit this pull request" and I don't know what else can be broken. @ulysses4ever, any ideas?

[ulysses4ever]

@mergify rebase

[mergify]

rebase

❌ Base branch update has failed

ulysses4ever token is invalid, make sure ulysses4ever can still log in on the Mergify dashboard.

[ulysses4ever]

@ulysses4ever, any ideas?

not really. Let's rebase via the github UI, perhaps? It worked fine and helped some times in the past. After that, the bot may be able to proceed..

[Mikolaj]

Thanks, I rebased via the UI button.

[Mikolaj]

@ulysses4ever, you are a wizard!