OTA updates production: Github workflows: production updates and rollback

### What is this about?
We now have a Github workflow to deploy OTA updates to preview channel. We need to have the similar workflow to deploy OTA updates to production channel.

- [ ] Github workflow to deploy OTA updates to production
- [ ] Github workflow to roll back OTA updates

### Scenario

_No response_

### Design

_No response_

### Technical Details

_No response_

### Threat Modeling Framework

_No response_

### Acceptance Criteria

_No response_

### Stakeholder review needed before the work gets merged

- [ ] Engineering (needed in most cases)
- [ ] Design
- [ ] Product
- [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [ ] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)

### References

_No response_

Start by locating the existing GitHub workflow that deploys OTA updates to the preview channel. Use it to understand the production deployment entry point and how a rollback could be triggered. Done means production OTA deployment and rollback workflows are implemented, with the required engineering review completed.

Written by the indexing model from the issue text.