feat: replace external syntax error position manually

[g-plane]

Advantages

• No need to construct large strings.
• Syntax error position will still be mapped to original position in HTML or template.

Disadvantages

• API changed: Error type from external formatter must be anyhow::Error instead of generic E, but this should be okay because most users will consume the built wasm instead of calling from Rust. Even though, most errors type can be converted to anyhow::Error.
• Error message recognition rule are encoded in a regex, and it may not be able to handle any external formatters. Of course, plugins listed in dprint.dev are supported.

Result

Given the code below:

<script lang="ts">


     {
</script>

<style>

    {
</style>

<script type="application/json">

   {
</script>

errors will be like:

Expected '}', got '<eof>' at file:///file.tsExpected '}', got '<eof>' at file:///file.ts:4:6

       {
       ~

       {
       ~
syntax error at syntax error at line 9, col 5: CSS rule is expected: CSS rule is expected
Line 14, column 4: Unterminated object

     {: Unterminated object

     {

Close #221

@UnknownPlatypus @sergey-kintsel

[netlify]

✅ Deploy Preview for markup-fmt ready!

Name	Link
🔨 Latest commit	94f616c
🔍 Latest deploy log	https://app.netlify.com/projects/markup-fmt/deploys/6a03b9aa396fb90008db27c6
😎 Deploy Preview	https://deploy-preview-223--markup-fmt.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[sergey-kintsel]

I ran the new version with the 10MB html file I mentioned before. it worked quite quickly - 1.9 seconds in total, didn't panic.
could we fix the output though? because right now the error message seems to be duplicating itself

syntax error at syntax error at line 199175, col 55: expect token `{`, but found `;`: expect token `{`, but found `;`