fix browser build sync and alive behavior for dev

[marionbarker]

• this matches main from PR 164 but started with dev branch of LoopWorkspace
• the code modification is identical to Fix sync alive #172 but has a different commit history

[marionbarker]

Summary

• Successful test
• LGTM

Detailed test record

Initial Configuration

• Use similar procedure as with Fix browser build sync and alive behavior #164 but no need to test the cron portion
• both marionbarker and loopdocs-tester started with main aligned with LoopKit main and dev aligned with LoopKit dev
• configure marionbarker:dev to have the changes in this PR and to set UPSTREAM_REPO to marionbarker instead of LoopKit
• sync loopdocs-tester to marionbarker so it has the same changes
• make a dummy commit (single line change in testflight) so marionbarker is one commit ahead of loopdocs-tester

State of alive branches

• Previously, I did a manual build of both main and dev for loopdocs-tester when main was aligned with LoopKit main and dev aligned with LoopKit dev
• therefore there are 3 alive branches:
  • alive-dev
  • alive-main
  • alive

Test

• run a manual build of loopdocs-tester:dev
• alive-dev was successfully updated
• manual build 34 succeeded
• https://github.com/loopdocs-tester/LoopWorkspace/actions

[marionbarker]

Closed in favor o PR #234