docs: Clarify build system specific features usage.

[FishAlchemist]

Summary

Since there are occasional inquiries about how to configure UV for build-system specific features, I want to raise awareness that users should refer to the documentation of the build system they are using for relevant settings.

Test Plan

Run docs service in local.
9821d58

[FishAlchemist]

However, if you have a better approach, please feel free to add a suggestion or create a separate pull request. If you think this is unnecessary, you can close this pull request directly.

If we require certain files to be included, we'll need to read the setuptools documentation for configuration options.

• How to include non-python files #10254

[zanieb]

Thanks!

I pushed 859b6b0 to give this some dedicated space

Is there more we should add here? I'm sure the bullets are not exhaustive as is. cc @konstin

[konstin]

There's also:

• dynamic metadata
• native code compilation
• partially: shared library vendoring/glibc compatibility/auditwheel (maturin integrates it, other backends expect the user to run auditwheel).

[FishAlchemist]

I just synced with main (git rebase main), but I don't know how to turn off signing commits.
By the way, have we considered running the uvx ruff version in CI? Because I really can't reproduce the error.

[FishAlchemist]

The issue seems to be related to ruff 0.9.0's handling of f-string expressions.

[konstin]

The error is not your fault, it's unrelated to your PR. The ruff 0.9 upgrade broke uv CI because uv CI doesn't pin ruff and it's getting fixed in #10433. Once that is merged we can rebase this PR on main and merge.