Docs: fix local assets path handling for Windows compatibility

[louismaximepiton]

Description & Motivation & Context

On Windows, I had some troubles having the examples working with extraCss or extraJs working on local. The solution was to add some \ in the path regex and it works fine on my side now.

Here is the rendering I have on main when I want to acces to the grid example:

Here is the trace I have in the terminal:

09:49:31 [ERROR] Failed to get example asset path from path: '**\bootstrap\site\src\assets\examples\badges\badges.css'.
  Stack trace:
    at sanitizeAssetPath (**\bootstrap\site\src\libs\examples.ts:64:11)
    at getExamplesAssetsRecursively (**\bootstrap\site\src\libs\examples.ts:53:7)
    at Module.getStaticPaths (**\bootstrap\site\src\pages\docs\[version]\examples\[...asset].ts:10:26)
    [...] See full stack trace in the browser, or rerun with --verbose.

with the change, it behaves correctly.

Type of changes

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

Checklist

• I have read the contributing guidelines
• My code follows the code style of the project (using npm run lint)
• My change introduces changes to the documentation
• I have updated the documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed

Live previews

• https://deploy-preview-41485--twbs-bootstrap.netlify.app/

Related issues

NA

[julien-deramond]

I don't have a Windows machine to test the before/after scenario myself, but I trust your judgment; Boosted uses the exact same configuration as Bootstrap.

The fix is minimal and specifically targets Windows compatibility. I’ve tested running the server locally, and compared the generated _site directory after running npm run docs; it’s identical, so there appears to be no impact from your change.

LGTM, let’s go ahead with it!