CI: add macOS app bundle distribution workflow

[nilason]

Add macOS app bundle distribution workflow, which sign, notarise and package to a dmg file.

At this point it "only" creates a GH artefact, which remains available three days.

[echoix]

Do we have other types of jobs that should run on the same triggers and we could group together in a "release.yml" workflow?

[nilason]

Do we have other types of jobs that should run on the same triggers and we could group together in a "release.yml" workflow?

Hopefully for Windows some time in the future, mid- to long-term. Definitely not in the short term.

[echoix]

Do we have other types of jobs that should run on the same triggers and we could group together in a "release.yml" workflow?

Hopefully for Windows some time in the future, mid- to long-term. Definitely not in the short term.

Related comment: #1212 (comment)

[echoix]

Does this workflow need to run as often in PRs (2min30) https://github.com/OSGeo/grass/actions/workflows/create_release_draft.yml

If we are to check if the release works once a week, on demand, plus on tags, checking release drafts is a good candidate

[nilason]

This is definitely not anything for PRs, and this artefact part will hopefully be replaced soon by an "upload to distribution server" step.

[echoix]

This is definitely not anything for PRs, and this artefact part will hopefully be replaced soon by an "upload to distribution server" step.

Oh nice! Was this discussed somewhere I missed?

[nilason]

This is definitely not anything for PRs, and this artefact part will hopefully be replaced soon by an "upload to distribution server" step.

Oh nice! Was this discussed somewhere I missed?

There are two builds which take ~45 min (ARM) and ~105 min (x86_64), involving uploading the whole package ~650 MB to Apple's server two time for each, so PRs are excluded from this. The upload to server part is my aim, which still have technical challenges to solve.

[wenzeslaus]

Does this workflow need to run as often in PRs (2min30) https://github.com/OSGeo/grass/actions/workflows/create_release_draft.yml

If we are to check if the release works once a week, on demand, plus on tags, checking release drafts is a good candidate

I think I made the release draft for each PR because PR would break the release workflow. I wanted and still want to simplify the release procedure as much as possible. Over years the release procedure accumulated ton of steps which were "let's just check this before the release" which resulted in extremely tedious list of steps.

[echoix]

There's no harm in trying it out, but I'd hope to see a consolidation of release jobs together if possible some day.

[nilason]

First batch ready, see https://github.com/OSGeo/grass/actions/workflows/macos_distribute_app.yml!