Mark pixi lock files as generated

[freundTech]

Closes #7108
Pixi is a cross-platform package manager for the conda ecosystem. It uses a lockfile called pixi.lock, which should be counted as generated code.

Description

Checklist:

• I am adding new or changing current functionality
  • I have added or updated the tests for the new or changed functionality.

[spenserblack]

Might want to check on this and make sure this is OK with the Pixi maintainers: prefix-dev/pixi#265 (comment)

[freundTech]

Might want to check on this and make sure this is OK with the Pixi maintainers: prefix-dev/pixi#265 (comment)

This PR and Issue #7108 have both been posted to the pixi discord server: https://discord.com/channels/1082332781146800168/1300274825838854235
While they haven't been explicitly approved by the pixi team they have been acknowledged.

Also the PR you linked is no longer up-to-date. As of prefix-dev/pixi#1488 pixi also adds linguist-generated to the .gitattributes file when initializing a project.

I also believe the answer in the PR you linked was given based on a misunderstanding:

I think it is very important people are aware a lock file changed in a PR.

Marking a file as generated doesn't hide that it changed in a PR. It just collapses it (just like large files are collapsed automatically). You can see that it changed, but you have to click to see what has changed.

[spenserblack]

Sorry if my comment came off as argumentative 🙂
I just wanted to bring that up because it reminded me of when the yarn maintainer asked that yarn.lock should not be generated.