️🛠 - Update CI/CD process with more automation

[maxwellmattryan]

Description

It would be amazing to have tagged releases with an automated build and deployment system. Although if I can't package it with an installer from within the GitHub workflow then it doesn't make sense, right? I may also want to test the final binaries before actually saying okay these are the ones we are going with.

This is the flow I am thinking:

• Create a tag and push to main or develop
  • Build is triggered and set to upload artifacts
  • Release draft is made
• Download and test release candidate artifacts
• Package artifacts with installers (if can't be automated)
• Upload installers to S3 bucket with versioning
• Distribute download URLs

Requirements

• Support Intel MacOS builds
• Support ARM MacOS builds
• Bump the GitHub actions MacOS version as high as possible
• Support Windows
  • Figure out Azure signing (reference Pamplejuce workflow)
  • Integrate installer
  • Figure out bash variable problem
• Use proper installer
• Separate into reusable and modular workflows / jobs
• Integrate Git tagging mechanism for triggering releases
• Add release drafting when tagged
• Add clang formatting
• Figure out how the installer fits into the flow
• Add distribution step(s) on release job
• Ensure tag protection is active
• Write page in Notion detailing all of this stuff for the future
• Use better Cloud Storage directory structure
  • Folder for each type of products then...
  • Folder for each product then...
  • Folder for each stage then...
  • Folder for each version with the corresponding installers