Fix: Resolve import globs safely on Windows paths

[taylortom]

Fix

• AdaptFrameworkImport built several glob patterns by interpolating a filesystem path (this.path / this.langPath) directly into the pattern string. On Windows the \ separators are interpreted as glob escape characters (and any glob-significant character in the path — [, (, * — breaks matching on every platform), so course directories, assets and plugins fail to resolve during import. Each path is now passed via the cwd option with a relative forward-slash pattern and absolute: true, posix: true (consistent with this file's /-based path handling and the already-safe cwd globs elsewhere in it).
  • prepare() — course directory discovery
  • loadAssetData() — asset metadata and manual asset listing
  • loadPluginData() — used content plugins
  • importCourseAssets() — asset file lookup

Testing

• Added a loadAssetData() test that drives the method with a course path containing glob-significant characters ([id]); it fails without the fix on all platforms.

[github-actions]

🎉 This PR is included in version 3.4.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀