chore(ci): build and test packaged app on the newer macos version COMPASS-8090

[kraenhansen]

Description

A friendly takeover of #5990 incorporating @mcasimir's feedback: #5990 (comment)

Updates the build variants used for packaging the app on MacOS to 14 and adds two new test variants for the MacOS 14. We might want to simply remove test-packaged-app-macos-11-arm and test-packaged-app-macos-11-x64 in the future.

Checklist

• New tests and/or benchmarks are included
• Documentation is changed or added
• I have signed the MongoDB Contributor License Agreement (https://www.mongodb.com/legal/contributor-agreement)

Motivation and Context

• Bugfix
• New feature
• Dependency update
• Misc

Open Questions

Dependents

Types of changes

• Backport Needed
• Patch (non-breaking change which fixes an issue)
• Minor (non-breaking change which adds functionality)
• Major (fix or feature that would cause existing functionality to change)

[gribnoysup]

Thanks! And seems like the flake I was seeing in my branch gone away, neat!

[addaleax]

Just for context, we've been building on a fairly low macOS version because we've felt that it gives us a better sense of guarantee that Compass will actually run on the macOS versions we claim to support. Currently, in our docs, that's 10.12 – which is definitely wrong at this point, Electron 27 raised the minimum to 10.15, so I'd recommend closing this ticket with "Documentation Changes Needed".

Now, I've chatted with some people in devprod before, but haven't really found anyone who is intimately familiar with what macOS's actual forward/backward compatibility story looks like in practice – i.e. answers to questions like "if we package on macOS 14, can we still relatively safely claim that it will run on 10.15 (or on 11, etc.)? Does it even really matter?".

All of which is to say: I think this change is fine, but in the long run we'll probably want to figure out what the actual story here is.