fix: markdown-it-attrs behaviour in pre wrapper plugin

[LiamEderzeel]

I noticed that the markdown-it-attrs did not work on fences with ```md. It was also mentioned in #826. The proposed changes could resolve this issue.

I tested the changes on the following markdown and also checked for compatibility with the highligh lines syntax.

<style>
.yellow {
  background-color: yellow !important; 
}
.yellow span {
  color: black !important;
}
</style>


Fix attributes for internal `preWrapperPlugin`

```css
<style>
.yellow {
  background-color: yellow !important; 
}
.yellow span {
  color: black !important;
}
</style>
```

````md
```md {data-attribute="some data" .yellow}
````

```md {data-attribute="some data" .yellow}
I made some custom styling for this code block through markdown-it-attrs

Also i added a custom attribute "data-attribute"

```

````md
```md {1}{data-attribute="some data" .yellow}
````
```md {1}{data-attribute="some data" .yellow}
I made some custom styling for this code block through markdown-it-attrs

Also i added a custom attribute "data-attribute"

```

````md
```md {1}
````
```md {1}
I made some custom styling for this code block through markdown-it-attrs

Also i added a custom attribute "data-attribute"

```

I also tested if disabling markdown-it-attrs still gives the expected behaviour.

export const shared = defineConfig({
  markdown: {
    attrs: {
      disable
    }
}

Let me know if changes are required or if more information is needed.

Resolves: #826

[LiamEderzeel]

I managed to reproduce the issue that makes the tests fail, ```md {1} without a trailing space produces behind the } fails to render. If you add a trailing space like so ```md {1} it will render just fine. It also seems to work fine if any other characters are behind the } like ```md {1}{}, ```md {1} {}, ```md {1}[], ```md {1} [], ```md {1}active, and ```md {1} active.

I'll do some more investigation soon.

[LiamEderzeel]

preWrapper failed to render because it tried to render an invalid attribute. This attribute is added by the highlightLines syntax {0}.

The highlightLinesPlugin already captures the highlightLines value from the attributes if it was parsed by markdown-it-attrs and re-applied it on token.info for the highlighter.

The changes from the last commit resolve this issue by removing the invalid attribute from the token.attrs.