🔧 Repository: Include Knip report check in CI

[04kash]

📜 Description

Introduce a CI check to ensure Knip reports are up-to-date.

• The check is opt-in for plugin maintainers. (similar to auto-version-bump workflow)

• Opt-in and behavior are configured via a BCP config file (e.g., .bcp.json).

CI check passes if:

• A Knip report is freshly generated and matches the current codebase.

CI check fails if:

• The Knip report is outdated or missing.

We could also enforce that the knip report should be empty, i.e. a new PR shouldn't introduce unused dependencies in the workspace.

👍 Expected behavior

A CI check to ensure that knip reports are kept up to date for opted-in workspaces.

👎 Current Behavior

There is no process to ensure that knip reports are kept up to date.

📃 Provide the context for the Bug.

No response

👀 Have you spent some time to check if this bug has been raised before?

• [x] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• [x] I have read the Code of Conduct

Are you willing to submit PR?

Yes I am willing to submit a PR!