Build a release bundle for macos

[tedinski]

Description of changes:

Add a "release bundle" CI step for macos as well.

Turns out, things just work! I opened #1067 to remind me about an issue that I initially thought would affect us, but only seems applicable to macos-arm. So, not relevant yet.

Resolved issues:

Resolves #1036

Towards #1045

Call-outs:

• Eventually we'll want to "refactor" how we do CI. IMO, we should run regressions on what we build with release bundle, then we'd just have these builds, and not the original ones... eventually.

Testing:

• How is this change tested? New CI. I did test downloading the artifact and running it locally, however.

• Is this a refactor change? no

Checklist

• Each commit message has a non-empty body, explaining why the change was made
• Methods or procedures are documented
• Regression or unit tests are included, or existing tests cover the modified code
• My PR is restricted to a single feature or bugfix

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

[celinval]

The reason why most people use debug build in regressions is because it has more checks like debug_assertions. It usually has more logs as well.

[celinval]

BTW, can you please add a comment why we do things differently on MacOS and Linux.