Move the demo app and forms into their own repo

[garethbowen]

The demo app was created for people to try out web-forms during development and on the website. With web-forms being included in central this is less necessary because it's easy to try it out. However it's still useful to have on the website.

• move the demo app into a new repo
• move all the demo forms that aren't required for testing into the new repo
• fix the GH action so it publishes the demo app onto the website
• update the GH action so it also gets the latest version of the webforms packages

[garethbowen]

Thinking about the GH action... We want a GH action in the new repo to build the demo app and then one in the website repo to deploy the app. For the first one, it should trigger when either the demo app code changes, or a new version of @getodk/web-forms is released to npm.

Something like...

on:
  push:
    branches:
      - main
  schedule:
    - cron: '0 0 * * *'

...

    steps:
      - uses: actions/checkout@v4
      - run: npm ci
      - name: Check for new version
        id: check
        run: |
          if [ "${{ github.event_name }}" = "push" ]; then
            echo "new_version=true" >> $GITHUB_OUTPUT
          else
            CURRENT_VERSION=$(node -p "node -p "require('./node_modules/@getodk/web-forms/package.json').version")
            NPM_VERSION=$(npm view @getodk/web-forms version --silent)
          
            if [ "$CURRENT_VERSION" != "$NPM_VERSION" ]; then
              echo "new_version=true" >> $GITHUB_OUTPUT
            fi
          fi
      - name: Publish
        if: steps.check.outputs.new_version == 'true'

...

[garethbowen]

Something like...

I'm thinking now a better approach would be to have one cron job which checks for the web-forms version and updates the package.json and package-lock.json and commits to the repo. Then have another job which is triggered by pushes that publishes the dist artifact.