Fix production deployment issues on main vs staging branch

[lparisc]

Current production deployment builds are launched manually from the docsgen staging branch. Since the docsgen repo contains documentation dependencies that affect content, the latest updates to the staging branch are affecting some content on the production builds.

AC: We need to deploy from main branch instead when deploying to production, but need to be careful:

• manually checkout the main branch
• run script to build to production
• verify correct deployment on web portal, else revert from backup
• manually checkout the staging branch again (or nightly staging builds will be affected)
• create ticket for long term solution

Long term solution is to add to scripts functionality to clone docsgen repo and checkout main when deploying to production, or staging when deploying to staging.

[lparisc]

Depends on #195

[lparisc]

Broken link:

• At https://staging-docs.eosnetwork.com/docs/latest/smart-contracts/getting-started/dune-guide/#create-test-accounts, end of 1st paragraph:
  • Accounts: https://staging-docs.eosnetwork.com/docs/20_smart-contracts/10_getting-started/20_Accounts.md

[lparisc]

Removing requirement to deploy to production in this ticket. Such requirement was moved to ticket #199. This allows to mark this ticket done and count the effort performed in fixing the staging vs. main deploy issues successfully, which were already tested locally.