updating cloud for release notes in asciidoc

[georgewallace]

Updating the conf.yaml for the cloud release notes that will be staying in asciidoc.

[github-actions]

A documentation preview will be available soon.

• 🔨 Buildkite builds
• 📚 HTML diff
• 📙 Preview page

Request a new doc build by commenting

• Rebuild this PR: run docs-build
• Rebuild this PR and all Elastic docs: run docs-build rebuild

_{run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.}

_{If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.}

[georgewallace]

@KOTungseth PR for the docs repo for the release notes. I think I got this right.

[lcawl]

If the builds pass, LGTM

[lcawl]

Seeing all these broken links makes me question whether rather than removing all the pages from https://www.elastic.co/guide/en/cloud/current/index.html (except release notes) is the right path forward or whether it's simpler to just create a "new" book that contains only the release notes. Since redirects are being created for all those pages, IMO that saves us from having to do all this clean up of broken links. I've created #3202 to test that alternative

[lcawl]

I think this can be closed since it's no longer required.

[florent-leborgne]

Just seeing this now as I was out when it was done. I think creating a new guide just breaks all URLs so it's not the ideal solution. If we want to avoid breaking all links could this work instead:

• Keep the currentSaas to the last cloud milestone branch containing asciidoc (ms-122 I believe)
• Hide (instead of delete) all non-release notes pages

@lcawl @georgewallace