Use -p instead of --release in Dune builds

[Leonidas-from-XIV]

We plan to slightly change the semantics of --release in Dune going forward (ocaml/dune#11378) thus we took a look whether and how it is used in OPAM repository.

My conclusion is that most packages can be just moved to -p (which implies --release) and it continues working fine. Thus I'm opening this PR to see if we can migrate the packages that use it off from --release and towards -p.

Some of the projects already use -p in newer versions (like ocaml-lsp-server), for the rest I can make PRs ustream if this works fine.

[mseri]

looks like llvm packages break if you build them with -p
Do you know why?

[Leonidas-from-XIV]

@mseri Hmm, looks like the CI logs are gone, I'll rebase (and remove the opsian fixes) and check the results.

[Leonidas-from-XIV]

@mseri The package does something strange, it does a rm llvm.install and then calls install.sh which does dune install. I've simplified it to just let build create the llvm.install and will see what the CI thinks about this.

[Leonidas-from-XIV]

That seems to have helped. There's some lower bounds failures and FreeBSD failures but it seems fairly unrelated and probably a separate issue.

[mseri]

I think it is all right with most of the packages to merge this change but I am worried about llvm. It is a complex package with complex build process that grew up workign around issues. I'd rather not touch llvm and instead have an upper bound on dune for those packages.

The maintainers can fix this and remove the upper bounds in the future once they make a new release

[Leonidas-from-XIV]

Ok, fair enough, I've removed the changes from llvm. The new versions of the package don't use dune, so I doubt that this will be a problem in the future.

(Wouldn't add a constraint on <3.18 just yet, we haven't merged the feature, this PR is mostly to prepare things)

[mseri]

Thanks a lot! If you let me know once this change is merged I will add the upper bound

[mseri]

Thanks