I'm very confused about what this PR is meant to do. It adds a new GH workflow file, modifies some tests and (seemingly) reformats unbox.rs?

I'm very confused about what this PR is meant to do. It adds a new GH workflow file, modifies some tests and (seemingly) reformats unbox.rs?

When this PR was submitted, without modifying tests and formatting unbox.rs, CI cannot pass.

It adds a new GH workflow file to build binaries for cargo-pgrx so that cargo-binstall could discover them.

Edit: removed now

The new workflow attaches binaries to our tagged releases, right?

#681 was kinda left in a bit of a nebulous state. @workingjubilee do we want to do this? I can only see this being useful if the consumer doesn't intend to upgrade cargo-pgrx very often.

The "resource constrained machines" bit over in #681 is compelling, I suppose, but it also takes some serious resources to use cargo-pgrx in any meaningful way, so... still not sure of the value.

There's little cost on our end, so I won't block this if you think it's a good idea.

I want to install cargo-pgrx without building it in CI, and it's why I prefer cargo binstall...