feat: add quarto cheat sheet setup to docs build actions

[Revathyvenugopal162]

cheat_sheet.pdf

[ansys-reviewer-bot]

Thanks for opening a Pull Request. If you want to perform a review write a comment saying:

@ansys-reviewer-bot review

[jorgepiloto]

Just some name suggestion:

[jorgepiloto]

This is great! I am more concerned about the versions showing up in the file. Any chance we can use Jinja here? We could have a cheat_sheet.qmd.tpl containing a {{ version }}. We render this via conf.py hooks so then it is built into the final cheatsheet. Also, we could include the code snippets we already have.

I know it is a bit of a burden but it alleviates all the maintenance of the docs.

[Revathyvenugopal162]

I understand this might be a bit challenging to implement, but I can give it a try.

[jorgepiloto]

This is great! Just left a comment on the automation of cheatsheets for this repo.

[jorgepiloto]

Thanks for the hard work with this, @Revathyvenugopal162. I just left some minor comments.

[jorgepiloto]

Do we really need to commit this file?

[jorgepiloto]

The syntax highlight for the YML code blocks in the cheatsheet seems to be the one for Python. Is it possible to change it to YML?

[jorgepiloto]

Fixing the highlight.

[jorgepiloto]

Thanks for adding all the suggestions, @Revathyvenugopal162. Let's update the references and merge this.

[jorgepiloto]

Is this required for Quarto to operate? This may be in conflict with packages declared inside of the libraries triggering the actions.

[Revathyvenugopal162]

We need jupyter to convert qmd files to pdf format

[jorgepiloto]

As discussed, projects should be the ones adding their doc-extensions in the required extra target.

[Revathyvenugopal162]

sure added it in d2b2f08, i will also add this requirement as a note in ansys sphinx theme docs