Add new workflow deployment for beta env

[gndelia]

Description

This PR adds a new workflow for a beta env. This env will be deployed after merging to main, similar to staging. This env does has

• Sentry disabled
• Analytics disabled (both umami and cookie3)
• no slack notifications during the deployment
• As this may be shared with some beta users, I specifically disabled the testnet functionality that's enabled on Staging (that's: There will be no Stake (in all its variations) nor Genesis Drop on testnet for this site)

Next step: I need to update the APIs for CORS

N/A

Checklist

• Manual testing passed.
• Automated tests added, or N/A.
• Documentation updated, or N/A.
• Environment variables set in CI, or N/A.

[Copilot]

Pull request overview

This PR introduces a new beta deployment environment that will be deployed automatically after merging to main, similar to staging. The beta environment is configured with analytics and Sentry disabled, no Slack notifications, and testnet functionality disabled to make it suitable for sharing with beta users.

Key Changes:

• Added a new deploy-beta job to the Hostinger deployment workflow
• Configured beta environment with analytics, Sentry, and testnet features disabled
• Set up deployment to use a separate target folder (HEMI_TARGET_FOLDER_BETA)