`is_explicit` removed from `pixi list` output

[renan-r-santos]

Checks

• I have checked that this issue has not already been reported.

• I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example

N/A

Issue description

No response

Expected behavior

Was the is_explicit field intentionally removed from the PackageToOutput struct in #5105? I couldn't find any info about this in the PR.

I'm asking because this partially broke the pixi-code VSCode extension, and I think to fix it I'd have to call pixi list twice to know which packages are explicit dependencies and which aren't, and that's a bit awkward.

[ruben-arts]

@baszalmstra I believe we shouldn't have removed that right?

[baszalmstra]

Yeah I dont know why that was removed??

[renan-r-santos]

Thanks for the quick feedback. I took a shot at fixing this in #5391.