build-sys: Use new tier = 2 for cargo-vendor-filterer

[cgwalters]

This fixes the problem described in the comment.

[cgwalters]

see also e.g.

• build-sys: Use new tier = 2 from cargo-vendor-filterer rpm-ostree#4429
• build: use new tier = 2 from cargo-vendor-filterer containers/bootc#104

[bgilbert]

Since this widens the set of platforms we're including, it could conceivably change the contents of the vendor tarball. Does it? If so, we should probably release-note the change to vendored platforms under "packaging changes".

Also, it looks like there are a few other packages that will need updates. Could you do those as well?

• afterburn - build-sys: Use new tier = 2 for cargo-vendor-filterer afterburn#934
• bootupd - build-sys: Use new tier = 2 for cargo-vendor-filterer bootupd#479
• ssh-key-dir - build-sys: Use new tier = 2 for cargo-vendor-filterer ssh-key-dir#152
• zincati - build-sys: Use new tier = 2 for cargo-vendor-filterer zincati#1003

[cgwalters]

Since this widens the set of platforms we're including, it could conceivably change the contents of the vendor tarball. Does it?

Just verified that there are no changes to the vendored crate set. It'd be surprising if there were - last I dug at this I didn't find any architecture-dependent crates, just platform dependent.

[bgilbert]

Okay, cool. This LGTM; leaving open so we don't forget to update the other projects in #1193 (comment).

[bgilbert]

Thanks for doing the other PRs. Once you get the Zincati one posted, I'll approve this.