bootstrap zephyr repack example

[valorkin]

Done definition for this repo bootstrap:

• should have RN + repack + zephyr application with instructions on how to run for ios and android
• should have rspack and webpack ways to be build
• should have host and at least one remote app
• should have github actions with e2e for both ios and adroind to check that we can:
  • build host and remotes (rspack/webpack) and it's deployed with zephyr
  • run host emu (without serving local host js bundles) where all bundles are consumed from zephyr
  • check that emu host renders host and remotes at least without errors
  • check that emu host consumed latest host and remotes from first ci step
• this repo has to be integrated with zephyr-package repo, so any PR merge to dev should trigger e2e scenario (it could be a new github action in zephyr-packaages)

[martamoc]

task moved to CS board (https://github.com/sgws-accelaration/sgws-mono/issues/318)

[MikitasK]

Sharing the update of this task:

@Esemesek

• Prepared RN + RePack + Zephyr application
• Added the documentation on how to setup and run the app
• Working on improving the documentation, UI and abstracting Federated Modules

PRs: #2, #4

@MikitasK

• Covered the application with E2E tests
• Configured CI/CD pipeline, for manual E2E tests trigger
• Fixing an issue with Android emulator on E2E pipeline (iOS part works fine)

PRs: #3

[MikitasK]

UPD: Android E2E tests pipeline is fixed

[MikitasK]

Sharing my current progress on this task for anyone who will take ower it:

• Updated E2E tests pipeline to support running on Debug and Release modes with Zephyr Repack Plugin enabled
• Figured out that zephyr-packages repo might be integrated into zephyr-repack-example as a submodule
• Came up with the strategy of building zephyr-repack-plugin locally
• Created draft PR (ci: Zephyr Repack Plugin E2E testing #8) with the basic setup of "Zephyr Repack Plugin E2E testing" CI/CD pipeline
• Created basic "Triggering" CI/CD pipeline for the zephyr-packages. Can't push it due to lack of write permissions, so here's the code that should be pushed:

name: Trigger Zephyr Repack Plugin E2E testing
on:
  push:
    branches:
      - main

jobs:
  trigger-origin:
    runs-on: ubuntu-latest
    steps:
      - name: Trigger 'Zephyr Repack Plugin E2E testing' workflow on 'zephyr-repack-example' repo
        uses: actions/github-script@v6
        with:
          script: |
            const response = await github.repos.createDispatchEvent({
              owner: 'ZephyrCloudIO',
              repo: 'zephyr-packages',
              event_type: 'trigger-from-zephyr-packages',
            });

The current flow is expected to be the following:
Trigger Zephyr Repack Plugin E2E testing workflow runs on the push to main at the zephyr-packages repo, which triggers the corresponding CI/CD pipeline at the zephyr-repack-example repo. This pipeline should:

1. Integrate zephyr-packages as a submodule
2. Build zephyr-repack-plugin locally
3. Link locally builded zephyr-repack-plugin as a dependency
4. Run E2E test on the release mode with zephyr-repack-plugin enabled
5. Report a status

Here's also the guide on how to generate Zephyr Auth Token:
https://github.com/ZephyrCloudIO/zephyr-documentation/blob/bd5273eb06ac5671297edadb245cb01983e9c8d2/docs/how-to/api-token.mdx