[ github-actions ] : Add workflow to get preview from fork repository and deploy to cf pages

[aialok]

What kind of change does this PR introduce?

• This PR introduces two workflows: one for preview deployment and another for production.
• We are transitioning from native Cloudflare app deployment to our own manual workflow for both preview and production deployments.
• Since Cloudflare does not support previews from forked repositories, we are implementing manual deployment via GitHub Actions.

Issue Number:

• Closes Get previews for PRs from forks #330

Screenshots/videos:

If relevant, have you updated the documentation?

Summary

• For complete details check out this comment : Get previews for PRs from forks #330 (comment)

Does this PR introduce a breaking change?

[AdrianGonz97]

Thanks for the consideration of using my action. Everything looks good to me!

All that's left to do is to:

1. generate an API key and add the Cloudflare credentials as env secrets
2. remove the existing github integration so that they don't conflict

---

I also want to reiterate what's said on the README regarding secrets and PR previews from forks:

If private secrets are being used during build time (which doesn't seem to be the case here) or at runtime for preview deployments (I can't tell from a glance, but it's viewable from Workers & Pages > YourSiteName > Settings > Environment Variables), then PR approvals should be added so that each deployment requires approval.

Taking a look at .env.example:

website/.env.example

Lines 1 to 2 in 7241449

	NEXT_PUBLIC_ALGOLIA_API_KEY=
	NEXT_PUBLIC_ALGOLIA_APP_ID=

it doesn't seem like any private secrets are being used, making preview deployments without pre-approval OK.

[aialok]

Thank you @AdrianGonz97 for your time and consideration.

I will be making the requested changes : )

[benjagm]

Let's try this! Great job Alok!