ci: automate formplayer build and bundle in Android workflow

[Bahati308]

Automate formplayer build and bundle in CI/CD workflow

Description

Add automated workflow to build and commit formplayer assets when formulus-formplayer
changes are merged to main/dev branches, eliminating manual synchronization PRs.

Changes:

• Add update-formplayer-assets.yml workflow that:
  • Triggers on formulus-formplayer/** changes to main/dev
  • Builds assets using npm run build:rn (automatically handles cleaning)
  • Commits updated assets to repository with [skip ci]
  • Only commits if assets actually changed
• Simplify formulus-formplayer upload:android script:
  • Remove redundant cleaning step (copy-to-rn.js already handles it)
  • Change from "build && clean && copy" to "build:rn"
• Update formulus-android.yml workflow:
  • Add paths-ignore for asset directory to prevent unnecessary builds
  • Prevent workflow loops from asset-only commits

This eliminates the need for developers to manually:

• Build formplayer assets locally
• Create separate PRs to sync assets to formulus
• Handle asset version conflicts from concurrent PRs

The CI now handles the entire asset synchronization process:

• Developers work on formplayer code and push changes
• When merged to main/dev, CI automatically builds and commits assets
• Formulus always contains the latest built assets from formplayer
• Android builds use committed assets (no build step needed in Android workflow)
• Developers get latest assets automatically on git pull

Type of Change

• Bug Fix
• New Feature / Enhancement
• Refactor / Code Cleanup
• Documentation Update
• Maintenance / Chore
• Other (please specify):

---

Component(s) Affected

• formulus (React Native mobile app)
• formulus-formplayer (React web app)
• synkronus (Go backend server)
• synkronus-cli (Command-line utility)
• Documentation
• DevOps / CI/CD
• Other:

---

Related Issue(s)

Closes/Fixes/Resolves:
closes #233

---

Testing

• Unit tests added/updated
• Integration tests added/updated
• Manually tested
• Tested on multiple platforms (if applicable)
• Not applicable

---

Breaking Changes

• This PR introduces breaking changes
• This PR does NOT introduce breaking changes

If breaking changes, please describe migration steps:

---

Documentation Updates

• Documentation has been updated
• Documentation update is not required

---

Checklist

• Code follows project style guidelines
• All existing tests pass
• New tests added for new functionality
• PR title follows Conventional Commits format

---

Thank you for contributing to Open Data Ensemble (ODE)!

[najuna-brian]

Hi @Bahati308 I have added a description to the issue for this PR, you can please have a look here
#233 (comment)

This PR looks like it builds and copies assets during CI, but only for the APK build, not for persisting the assets in formulus
Would it be nice if:
The assets would be committed to formulus after the formplayer changes are merged, so that:
Formulus always has the latest built assets from formplayerand when the Android app builds, it uses these committed assets?

[najuna-brian]

The workflow builds assets but doesn't persist them. Could we add a git commit step after the build to push assets to formulus, ensuring local developers get latest changes on pull.

Thoughts?

[r0ssing]

Hello. Thank you for this! It will really help us ensure consistency and eliminate human error from this part..
@najuna-brian: Very thoughtful input. I agree that it would make sense to have the assets committed as well - to further eliminate the risk of human (or rather developer 😎 ) error 😄

[Bahati308]

The workflow builds assets but doesn't persist them. Could we add a git commit step after the build to push assets to formulus, ensuring local developers get latest changes on pull.

Thoughts?

Thanks for the great review @najuna-brian , it was insightful and the updates have everything up and running.

[r0ssing]

Great work!

[r0ssing]

backmerged..