docs: list supported sdist formats

[mkniewallner]

Summary

Explicitly list the formats and extensions that uv supports, based on this list. Not a huge fan of adding the section in concepts/resolution.md, but I did not find a better place. Alternatively we could maybe add a dedicated page that shortly explains Python package types (wheels, sdists), where such a section could live?

Test Plan

Local run of the documentation.

[mkniewallner]

Initially wanted to also add a link to the new section here, but the code generating markdown pages outputs all links with <a> HTML tags, which made it not possible to have both a correct link and mkdocs not complaining about the link not existing in strict mode. Since there are no other links to other internal pages here and in settings.rs, I assumed that this is simply not yet supported by the code generating markdown pages, so left this out for now.

[zanieb]

This seems like a reasonable place to me right now. I guess we'll need like a "Distributions" concept page? Now that we have a uv build command it makes a bit more sense. I can open a tracking issue for that.

Should we say "i.e." or "e.g." instead of "usually" in those CLI docs?

[mkniewallner]

Should we say "i.e." or "e.g." instead of "usually" in those CLI docs?

Good idea, went with .e.g. since it's a subset of the actually supported formats, so thought it makes more sense.

[zanieb]

Charlie will want "e.g.," haha (per our style guide)

[mkniewallner]

Charlie will want "e.g.," haha (per our style guide)

Thanks to that, TIL about yet another thing that is different between American and British English 😄 https://jakubmarian.com/comma-after-i-e-and-e-g/

[charliermarsh]

Thanks!

[konstin]

We should clarify that PEP 625 has decided that .tar.gz is the canonical source distribution filename, all other extensions should be considered legacy or experimental.