Sync the upstream-downstream ./asciidoc content

For more information, refer to Creating release branches for RHBQ documentation procedure.

The contents of the ./asciidoc folder must come from a specific community release branch. The preceding process should take care of this correctly. However, if there’s any doubt or if the timing of the product release branch is off, you can delete the contents of the ./asciidoc folder and then run the appropriate pipeline job for that branch.