Mark more tools commonly necessary for builds and config or build-only deps as build-tools

[trws]

This came from #42082, but seems like something we probably want. The main thing is this allows the concretizer to duplicate these where necessary, and they're used as build tools with only build type extremely frequently near the bottom of the stack. Some of those deps are actually dev-only, but we don't have a good way to express that right now so I'm leaving them alone, but at least marking these so we can solve around them.

[spackbot-app]

Hi @trws! I noticed that the following package(s) don't yet have maintainers:

• pkgconf
• sed

Are you interested in adopting any of these package(s)? If so, simply add the following to the package class:

    maintainers("trws")

If not, could you contact the developers of this package and see if they are interested? You can quickly see who has worked on a package with spack blame:

$ spack blame pkgconf

Thank you for your help! Please don't add maintainers without their consent.

You don't have to be a Spack expert or package developer in order to be a "maintainer," it just gives us a list of users willing to review PRs or debug issues relating to this package. A package can have multiple maintainers; just add a list of GitHub handles of anyone who wants to volunteer.

[trws]

@adamjstewart, are the py-torchdata errors something a bounce would deal with or should I be looking at a force-merge?

[adamjstewart]

They are not, working on a PR to fix this now, thanks for letting me know.