fix: update tm language with new markdown frontmatter specs

[mcanouil]

From #501 (comment)

FrontMatter integration should be updated to match Markdowns

quarto/apps/vscode/syntaxes/quarto.tmLanguage.yaml

Lines 226 to 231 in 06678d5

	frontMatter:
	begin: \A-{3}\s*$
	contentName: meta.embedded.block.frontmatter
	patterns:
	- {include: source.yaml}
	end: (^|\G)-{3}|\.{3}\s*$

microsoft/vscode-markdown-tm-grammar#162

https://github.com/microsoft/vscode-markdown-tm-grammar/blob/main/markdown.tmLanguage.base.yaml#L202-L216

Fixes #501, fixes #504, fixes #505

[mcanouil]

I'm not entirely sure this is enough as running yarn dev-vscode and running the extension with this change does not seem to fix the issue but I might be missing something in the setup/use of the extension in a development setting.

Edit: I've figured the missing step: node apps/vscode/syntaxes/build-lang.js
I confirmed in the debug mode that the issue is gone.

[mcanouil]

Also tracking the TM language change on Positron side:

• Frontmatter integration update for Markdown (Quarto integration) posit-dev/positron#4237

[juliasilge]

The .vsix built from this PR works fine with the current release build of Positron. See some details here.

Positron won't merge the upstream Code OSS release until later this week FYI.

[juliasilge]

We will want to bump the Quarto extension version at the same time that we merge in upstream Code OSS if possible.

[mcanouil]

Feel free to take over the PR to make the additional changes you might need (or make another PR after this one).

[juliasilge]

Edited to clarify:

From my perspective, this PR is ready to go and can be merged. ✅

Additionally perhaps separately, it would be nice to update the extension version in this repo so it makes a bit more sense for dev work. The .vsix says this is version 1.111.0 but the current release is 1.113.0

[mcanouil]

Let me grab a laptop.

[mcanouil]

I've bumped the version to 1.114.0 (minor) and added a changelog entry.

[mcanouil]

@juliasilge FYI, I don't have any permission here so I cannot proceed further.

[andyatsenversa]

I just updated my VSCode extension - and no more red text, the fix appears to be working.
Thanks everyone