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 a new extension to a language.

  • The new extension is used in hundreds of repositories on GitHub.com
    • Search results for each extension:
      • https://github.com/search?type=code&q=NOT+is%3Afork+path%3A*.FOOBAR+KEYWORDS
  • I have included a real-world usage sample for all extensions added in this PR:
    • Sample source(s):
      • [URL to each sample source, if applicable]
    • Sample license(s):
  • I have included a change to the heuristics to distinguish my language from others using the same extension.

• I am adding a new language.

  • The extension of the new language is used in hundreds of repositories on GitHub.com.
    • Search results for each extension:
      • https://github.com/search?type=code&q=NOT+is%3Afork+path%3A*.FOOBAR+KEYWORDS
  • I have included a real-world usage sample for all extensions added in this PR:
    • Sample source(s):
      • [URL to each sample source, if applicable]
    • Sample license(s):
  • I have included a syntax highlighting grammar: [URL to grammar repo]
  • I have added a color
    • Hex value: #RRGGBB
    • Rationale:
  • I have updated the heuristics to distinguish my language from others using the same extension.

• I am fixing a misclassified language

  • I have included a new sample for the misclassified language:
    • Sample source(s):
      • [URL to each sample source, if applicable]
    • Sample license(s):
  • I have included a change to the heuristics to distinguish my language from others using the same extension.

• I am changing the source of a syntax highlighting grammar

  • Old: [URL to grammar repo]
  • New: [URL to grammar repo]

• I am updating a grammar submodule

• I am adding new or changing current functionality

  • I have added or updated the tests for the new or changed functionality.

• I am changing the color associated with a language

  • I have obtained agreement from the wider language community on this color change.
    • [URL to public discussion]
    • [Optional: URL to official branding guidelines for the language]

[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.