ci(js-peer): deploy static site to GitHub Pages

[NiKrause]

Summary

This switches the js-peer deployment path from the current static Storacha/IPFS workflow to GitHub Pages.

It also fixes the broken project-site asset paths so the static app works correctly when served from a repository subpath like:

• https://nomadkids.github.io/universal-connectivity/

Fixes #342

What changed

• replace the js-peer publish workflow with the official GitHub Pages Actions flow
  • actions/configure-pages
  • actions/upload-pages-artifact
  • actions/deploy-pages
• keep PRs as build/lint validation only
• deploy main to GitHub Pages
• add GitHub Pages-aware basePath / assetPrefix
• fix static logo asset paths so they resolve correctly on a project page

Why

The current js-peer app is a static Next.js export, so GitHub Pages is a straightforward deployment target and fixes former Storacha/IPFS for this frontend which stopped providing services.

Preview

Preview fork deployment:

• https://nomadkids.github.io/universal-connectivity/

Important setup note

GitHub Pages must be enabled for the repository, and the publishing source must be set to GitHub Actions.

Without that, actions/configure-pages@v5 fails with a Get Pages site failed / 404 Not Found error.

Enable in GitHub UI

Go to:

• Settings
• Pages
• Source -> GitHub Actions

Enable with GitHub CLI

If Pages has not been created yet:

gh api -X POST repos/libp2p/universal-connectivity/pages \
  -f build_type=workflow