Add Typst support with feature parity to HTML and LaTeX PDF

[cderv]

closes #31
closes #36

This builds on #36 and work by @elipousson

This PR

• does keep the basic support added in Add typst support (#31) #36 but remove the color addition (to be dealt with in Added support for color (?) #35 )
• It does also rebase on latest dev version (with v6.7.2 support in HTML and LaTeX)
• And it adds feature parity support with current state of extension, meaning
  • All CSS sizing for HTML needs to be supported with em conversion in typst. Values from the CSS are used
  • Default icons in this extension are solid type. Typst package default to regular so this is changed.
  • FA v6 is configured as v7 is not yet supported

This PR seems to be ok and produce this PDF
example-typst.pdf

However, I am puzzled because we're missing font handling.

• Docs says that fonts needs to be installed and they are not shipped (https://typst.app/universe/package/fontawesome#usage)
• But document still renders with unicode (at least on windows) while I don't have the font installed

Also, while doing quarto render I don't see warning. but adding keep-typ: true and calling quarto typst compile does show expected message

❯ quarto render .\example.qmd --to typst
pandoc 
  to: typst
  output-file: example.typ
  standalone: true
  shift-heading-level-by: -1
  default-image-extension: svg
  wrap: none
  citeproc: false
  variables: {}

metadata
  title: Font Awesome Quarto Extension

[typst]: Compiling example.typ to example.pdf...DONE

Output created: example-typst.pdf

❯ quarto typst compile .\example.typ
warning: unknown font family: font awesome 6 free solid
   ┌─ @preview/fontawesome:0.6.0\lib-impl.typ:80:12
   │
80 │       font: default_fonts, // If you see warning here, please check whether the FA font is installed
   │             ^^^^^^^^^^^^^

warning: unknown font family: font awesome 6 brands
   ┌─ @preview/fontawesome:0.6.0\lib-impl.typ:80:12
   │
80 │       font: default_fonts, // If you see warning here, please check whether the FA font is installed
   │             ^^^^^^^^^^^^^

warning: unknown font family: font awesome 6 free
   ┌─ @preview/fontawesome:0.6.0\lib-impl.typ:80:12
   │
80 │       font: default_fonts, // If you see warning here, please check whether the FA font is installed
   │             ^^^^^^^^^^^^^

So we need a way to provide new font in Typst font path from an extension. Probably related to

• Quarto Lua API - add quarto.doc.use_typst_package() quarto-dev/quarto-cli#13518

So maybe Typst support needs to wait for 1.9 ?

[elipousson]

This is great. Thank you for picking up the PR and running with it!

[cderv]

So @gordonwoodhull explained me why this works without having the font path. This is because we do use fontawesome in Quarto CLI for callout, and for that we do already provide the FA v6 fonts in Typst font path.

So there is no need to handle font directly in this extension.

However, there is a topic of using this extension with callouts as two different version of the typst package will be loaded... 🤔