fix(content): failed ci on windows and enhance file name detection regex

[jefrydco]

Types of changes

• Bug fix (a non-breaking change which fixes an issue)
• New feature (a non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

This PR do 2 things:

1. Fix failed CI build on windows.
   Last time we added custom highlighter, the test case always make the CI failed on Windows. After long debugging, I found that the culprit was shiki twoslash always renders a custom link to TypeScript playground for each code block. I don't know why the custom link is generated a little bit random although the code isn't changed in Windows. It doesn't work that way in Linux or Windows, the link will always be same. That's why the CI isn't failed in Linux and Mac. So I decided to remove that link to make the test case worked.

To give more context @benjamincanac and I already discussed here #467 .

2. Enhance file name detection regex
   Using previous method, this code won't parsed correctly:

```typescript {}[something.ts] somemeta
console.log('Hello World')

By default we already parsed language, line highlight and file name. And actually we can still add our custom data/identifier there. In new custom highlighter syntax we can get that value through node:

export default {
  content: {
    highlighter(rawCode, lang, thematicBlock, astUtility) {
      const { node } = astUtility
      const { meta } = node 
      // meta here contains "somemeta" above
    }
  }
}

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes (if not applicable, please state why)

[Atinux]

Beautiful work!