Feature Request: Let's move the guides.dataverse.org build from Jenkins into GitHub Actions

Overview of the Feature Request
Currently, the guides are built by: https://jenkins.dataverse.org/ which uses a .pem to initiate a Sphinx build, log onto the guides server, and unzip it onto the server. The intention is to move away from this process into a more open/controllable build into GitHub Actions. An AWS IAM role could be a possible direction to move away from the pem. This is part of a wider effort by UNC to make Jenkins redundant.

What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
Solely intended for community members and developers

What inspired the request?
Organizational mandate from UNC through the Research Data Management Core to retire the Jenkins server.

What existing behavior do you want changed?
The Jenkins build step for Dataverse Guides

Any brand new behavior do you want to add to Dataverse?
Yes, a new GitHub Actions workflow that performs the same build steps.

Any open or closed issues related to this feature request?
N/A

Are you thinking about creating a pull request for this feature?
Yes our organization, The RDMC, (specifically me and @donsizemore) will assume ownership of the feature and the Pull Request if this issue is approved by IQSS maintainers.

Start by reviewing the existing guides build at jenkins.dataverse.org and the contributor information linked in the issue. The work is complete when a GitHub Actions workflow performs the same Sphinx build and deployment steps without the Jenkins build step or its .pem-based process.