Move scripts from old website to CI

[aliabd]

This PR creates a new workflow in the ci that:

• uploads a wheel of the library to aws on every commit to main
• uploads all the website demos to spaces on every commit to main (with _main suffix)
• uploads all the website demos to spaces when a new version is released (no _main suffix)

I tested the workflow on a fork of this repo and finally got it working fine here, and all the spaces were updated correctly.

Also makes some related changes:

• Adds LoginButton, LogoutButton, and DuplicateButton component demos, and fixes issues with other component demos.
• Fixes model3d guide and broken demos inside it.
• Removes an old workflow that used to create the docs when a new gradio version is released on the old website.

Closes: #5204 #5211 #5255

[gradio-pr-bot]

🪼 branch checks and previews

•	Name	Status	URL
	Spaces	ready!	Spaces preview
	Website	ready!	Website preview
	Storybook	ready!	Storybook preview
	Visual tests	all good!	Build review
🦄	Changes	detected!	Details
📓	Notebooks	matching!

---

Install Gradio from this PR

pip install https://gradio-builds.s3.amazonaws.com/a7fef65ebf9f10813ccd49e50fad5b71a444bfd8/gradio-3.41.2-py3-none-any.whl

Install Gradio Python Client from this PR

pip install "gradio-client @ git+https://github.com/gradio-app/gradio@a7fef65ebf9f10813ccd49e50fad5b71a444bfd8#subdirectory=client/python"

[gradio-pr-bot]

🦄 change detected

This Pull Request includes changes to the following packages.

Package	Version
gradio	minor
website	minor

• Maintainers can select this checkbox to manually select packages to update.

With the following changelog entry.

Move scripts from old website to CI

Maintainers or the PR author can modify the PR title to modify this entry.

Something isn't right?

• Maintainers can change the version label to modify the version bump.
• If the bot has failed to detect any changes, or if this pull request needs to update multiple packages to different versions or requires a more comprehensive changelog entry, maintainers can update the changelog file directly.

[pngwn]

Can we reuse the existing upload_demo_to_spaces script and extend the build/deploy PR workflow (adding a push: branches: -main event and changing the demos based on the event)? These changes are mostly duplicates of those files.

[freddyaboulton]

Can we reuse the existing upload_demo_to_spaces script and extend the build/deploy PR workflow build/deploy PR workflow

Makes sense!

[aliabd]

@pngwn @freddyaboulton I got this working, removed the new workflow and instead worked it into build-pr/deploy-pr-to-spaces. I did keep the script though as it does a bunch of stuff differently from upload_demo_to_space.

I tested the on a fork here:

• Example of build-pr and deploy-pr-to-spaces working fine in this PR. You can see spaces used the correct wheel representing the right commit inside the PR.
• Example of build-pr and deploy-pr-to-spaces working fine when the same PR got merged. You can see all the website demos used the correct wheel representing the right commit to main.

(Note there are small differences between the code here and on the fork: basically was easier to test with a different aws bucket I control so tried it there with a different s3 url, but will use @freddyaboulton's bucket here)

[freddyaboulton]

Thanks @aliabd ! Looks good to me!