Maintenance: phase out docs publishing to GitHub Pages

[dreamorosi]

Summary

To complete the migration to the new GitHub Org and docs infrastructure, we need to remove from the Docs workflow all the steps that push the docs to GitHub pages, as well as disabling the feature in the repo settings.

Why is this needed?

So that the docs are published only to the new destination.

Which area does this relate to?

Automation

Solution

No response

Acknowledgment

• This request meets Powertools for AWS Lambda (TypeScript) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET

Future readers

Please react with 👍 and your use case to help us understand customer demand.

[dreamorosi]

The versions.json file in the repo doesn't match with the one in S3 (1.9.0 and its latest alias are missing).

This results in the docs not being available for the latest version.