Rename repo to `sage-monorepo`

[tschaffter]

Now that the folder structure welcomes multiple projects, renaming the repo should help making other projects like Schematic at home.

• [x] Rename repo
• [x] Update references to the repo name
  • CI/CD workflow
• [x] Rename workspace commands in dev-env.sh
• [x] Provide commands to team members on how to update their dev environment
  • update remote
  • rename folder

[tschaffter]

Steps that developers need to perform after renaming the repo

On GitHub:

• Rename fork repo to sage-monorepo

Locally:

1. Push work in progress to your origin` remote
2. Stop the running dev container and remove corresponding container and volume.
3. Check your existing remotes.

   $ git remote -v
   origin  https://github.com/tschaffter/challenge-registry.git (fetch)
   origin  https://github.com/tschaffter/challenge-registry.git (push)
   upstream        https://github.com/Sage-Bionetworks/challenge-registry.git (fetch)
   upstream        https://github.com/Sage-Bionetworks/challenge-registry.git (push)

4. Update the URL of the origin and upstream remote.

   git remote set-url origin https://github.com/YOUR_USERNAME/sage-monorepo.git
   git remote set-url upstream https://github.com/Sage-Bionetworks/sage-monorepo.git

5. Verify the URL of your remotes.

   $ git remote -v
   origin  https://github.com/tschaffter/sage-monorepo.git (fetch)
   origin  https://github.com/tschaffter/sage-monorepo.git (push)
   upstream        https://github.com/Sage-Bionetworks/sage-monorepo.git (fetch)
   upstream        https://github.com/Sage-Bionetworks/sage-monorepo.git (push)

6. Rebuild and open the dev container.
7. Switch to the main branch and update it from the upstream remote.
   • If this operation fails, it's probably because to the commands run by the git hooks. Try to find a workaround to update your main branch.
8. Remove the folder node_modules.
9. Run the command workspace-install to install the dependencies (Node.js, Java, Python)
10. TEST: Start the challenge registry with nx serve challenge-registry-app and check that the app is accessible in the browser.