Align workflows with openSUSE/doc-ci

[ranjinimn]

This updates the validate/build workflows to align with openSUSE/doc-ci and move away from the current usage of a personal docker image (which is now unmaintained and likely outdated)

[ranjinimn]

@hardys This is in continuation with the conversation we had about the replacement for the daps script that Andrew Garcey had created.
I worked with my team and he guided me to complete this.
Please let me know if you have any questions. If we are good to go, please approve, and then I will merge this PR.

[ranjinimn]

@hardys Now the PR is ready for review. Please let me know if you have any questions.

[hardys]

Thanks a lot for the work on this! I have two questions:

• How can we replace the preview currently published at https://suse-edge.github.io/ (this PR removes the workflow to update it, can we either reinstate it, or propose an alternative approach?)
• Is it possible to update the local build instructions to align with this new workflow? https://github.com/suse-edge/suse-edge.github.io?tab=readme-ov-file#how-to-testbuild-locally

[ranjinimn]

Thanks a lot for the work on this! I have two questions:

• How can we replace the preview currently published at https://suse-edge.github.io/ (this PR removes the workflow to update it, can we either reinstate it, or propose an alternative approach?)
• Is it possible to update the local build instructions to align with this new workflow? https://github.com/suse-edge/suse-edge.github.io?tab=readme-ov-file#how-to-testbuild-locally

@hardys Thank you for the feedback. I have edited the script to publish on https://suse-edge.github.io/. Once the PR is merged, we will need to monitor to check if it gets published there.
Regarding the local build, it is already documented in https://github.com/suse-edge/suse-edge.github.io/tree/main/asciidoc#building-the-suse-branded-version-locally. I can remove the content in the present file and add the link to remove obsolete information.

[hardys]

@ranjinimn this needs a rebase but otherwise as recently discussed I think it's likely ready to merge?

I modified the title and description, feel free to adjust further if I missed anything, thanks!

[ranjinimn]

@hardys I checked with Toms and he mentioned that the changes you made in #1059 is not needed for docbook.yml file.

[ranjinimn]

@hardys Also, Is it okay if I close this and create a new PR? I have ended up in conflicts on this and is taking time to resolve.