ScanCode next workflow

We are doing and end of year 2026 push to fix many pending issues across ScanCode toolkit and ScanCode.io and their related and sub-repos. This is tracked in this project board https://github.com/orgs/aboutcode-org/projects/52/views/49

• @hesa plans the iterations and assign issues to the project board and the iterations
• you grab an issue and assigns it to yourself. Do not grab the top level issues that have an issue_id and a title starting with scancode-next
• if an issue is likely to take more than couple days worth of work and cannot be completed in the iteration, then break it down in one or more smaller child sub issues (related to that parent issue). Ensure that the child issues are also added to the project board with a "scancode-next" project_id.
• if you want or need to work on issues that are not yet in the board sync up quickly with @hesa
• when done, write a last completion comment explaining the work as we do usually, and close the issue.