PDF: `{.callout}` div with heading and footnote different from HTML output

[fitzchivalrik]

Bug description

Using a {.callout} div with a headline and footnote in HTML results in the expected output of a callout block without an icon,
the provided headline and a footnote at the end of the document.
Rendering the same example to PDF via Latex results in unexpected output (see images).

Minimal example:

---
format: pdf
---
# Document Title

Text with a footnote^[saying nothing at all.].

::: {.callout}

## Not visible in PDF output

Some text without a footnote.

:::

::: {.callout}

## Still not visible in PDF output

A footnote^[which is inside the callout instead of outside.].

:::

On Pop!_OS 22.04 LTS 5.17.5-76051705-generic #202204271406~1653440576~22.04~6277a18
Quarto check output

[✓] Checking Quarto installation......OK
      Version: 0.9.628
      Path: /opt/quarto/bin

[✓] Checking basic markdown render....OK

[✓] Checking Python 3 installation....OK
      Version: 3.10.4
      Path: /usr/bin/python3
      Jupyter: 4.10.0
      Kernels: java, python3

[✓] Checking Jupyter engine render....OK

[✓] Checking R installation...........OK
      Version: 4.1.2
      Path: /usr/lib/R
      LibPaths:
        - /usr/local/lib/R/site-library
        - /usr/lib/R/site-library
        - /usr/lib/R/library
      rmarkdown: 2.14

[✓] Checking Knitr engine render......OK

Checklist

• formatted your issue so it is easier for us to read?
• included a minimal, self-contained, and reproducible example?
• documented the quarto version you're running, by providing the output produced by quarto check in a terminal in your issue?
• documented the RStudio IDE version you're running (if applicable), by providing the value displayed in the "About RStudio" main menu dialog?
• documented which operating system you're running? If on Linux, please provide the specific distribution as well.
• upgraded to the latest version, including your versions of R, the RStudio IDE, and relevant R packages?

[jjallaire]

Thanks for reporting this. We are finishing up our v1.0 release right now but should be able to fix this for our v1.1 release.