fix(license.lua): correct license metadata lua processing

[mcanouil]

Correct the processing of license metadata to ensure proper handling of inline license elements.

The typo prevented from using license.text in template/partials/shortcodes when license: "my license" was used.

Note that version is not added to "text" for CC0 licenses because for some reason, the URL/parsing is created in TypeScript for this license.

---
format: html
license: "Whatever"
---

{{< meta license.text >}}

---
format: html
license: "CC BY"
---

{{< meta license.text >}}

---
format: html
license: "CC0"
---

{{< meta license.text >}}

[posit-snyk-bot]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[cderv]

Thank you for the change!

Honestly, I don't think this is a typo - text was just not set initially.

Then it was added for the typescript part in #6784.

So this change is an improvement to make inline CC license having a default text, exactly like with the appendix part.

This is good ! Another oversight is the the support for CC0 that was added only on the TS part too: #10763

---
format: html
license: "CC0"
---

License: {{< meta license.text >}}

so it won't be CC0 1.0 like the link

Also, I checked the template for which those meta are used. I think this is fine to add such text. Only JATS seems to use this licence in template. And <license-p> seems to support this text for CC too https://jats.nlm.nih.gov/publishing/tag-library/1.3/element/license-p.html

[mcanouil]

FWIW, the context was for my Typst template, I wanted to show license/copyright, but this prevented it and generally it prevented anyone to use it as part of their template.

[cderv]

Thanks for the context, that it helpful to understand ! I'll merge this today

[mcanouil]

And yes, CC0 is not accounted for as it would require more thinking and possibly refactoring to move it to Lua with other license processing. Maybe worth opening an enhancement issue for "future"?

[mcanouil]

The typo I was referring to is (the brackets should not be there):

• https://github.com/quarto-dev/quarto-cli/pull/13832/changes#diff-42d0469b5f06355473cc5c74a61ee7c1888ef1a7423ace4a3bbc3d3439b8bd2aL162

The other changes are only for CC licenses.