Ship `plan.json` with release artifacts

[hasufell]

plan.json allows to examine what was actually built and possibly reproduce release artifacts. It also allows easy examination of compile time flags (e.g. which pugins were built).

[jneira]

As discussed in irc:

• the file could be included in the binary via TH and printed with a cli option (good suggestion by @hasufell)
• stack does not produce the file so we should not add the cli option or output a warning if we build the executable with

[hasufell]

Here's a straight-forward implementation that you might be able to just copy-paste: https://gitlab.haskell.org/haskell/ghcup-hs/-/commit/e9c335eeccb30b0f2fa4d8ce1ba2764bf9b7269b

[michaelpj]

I think we probably don't want to do this?

[hasufell]

I think we probably don't want to do this?

Why?

[michaelpj]

Because we can't do it reliably and it's not clear what it's for?

[hasufell]

Because we can't do it reliably and it's not clear what it's for?

It's reliable, because it's meant to work for the release CI, which uses cabal. It's useful for debugging bugs and other issues. cabal also used to ship plan.json with its releases.

[hasufell]

But this isn't really anything high-priority. If people have a strong opinion, I suggest we just ship plan.json with the release artifacts.