chore: Adding workflows for automated releases

[ruisebas]

Description of changes:
This PR adds the release_authenticator.yml and release_kickoff.yml workflows automating the Release process.
Also adding the corresponding Fastlane files.

This is their behaviour:

• Kickoff release: Is manually triggered through the Actions tab and takes care of updating the changelog, updating the ComponentInformation and creating a PR into main with these changes for the maintainer to review and merge
• Release Authenticator: Is automatically triggered on any push to main. When the commit is a result of the previous kickoff PR being merged, a stable releases is performed; all other commits result in an unstable release.
  • Stable release: Follows SIMVER and is either a major, minor or patch release
  • Unstable: a.k.a. pre-release. It basically just contains the latest in main with a tag with format X.Y.Z.unstable.i, with X.Y.Z being the next tentative version and i the current iteration of unstable releases.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 41.89%. Comparing base (a98f1c6) to head (a562e5f).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #68   +/-   ##
=======================================
  Coverage   41.89%   41.89%           
=======================================
  Files          41       41           
  Lines        1857     1857           
=======================================
  Hits          778      778           
  Misses       1079     1079           

Flag	Coverage Δ
Authenticator	41.89% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[harsh62]

Use an action instead of an inline script (recommended). For more information visit https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions#good-practices-for-mitigating-script-injection-attacks

Event context data that are user controlled must be treated as potentially untrusted input. For more information visit https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions#understanding-the-risk-of-script-injections

[harsh62]

Security risk needs to be addressed.