Indexer: Escape special characters in storyImport regex

[VojGin]

Closes #

No issue in evidence

What I did

I had a problem with using <Meta of{...} /> inside MDX file.

It always resulted in this error and I didn't know why.

Turns out the problem was the string literal inserting in the Regex as it did not escape special characters from the file path thus it could never match.

Usually paths have slashes / which work fine without escaping. But I had a plus sign + in my path. A plus sign is regex modifier, thus the regex stopped working.

How to test

1. Run unfixed storybook on a project with plus sign + somewhere in the absolute path and try to include some MDX containing <Meta of={...} />

Such as this one:

{/* ButtonDocs.mdx */}

import { Meta, Story } from '@storybook/blocks';
import * as ButtonStories from './Button.stories';

<Meta of={ButtonStories} />

2. It will result in an error.

3. You can compare it then with the fixed version then. The error is gone.

Checklist

• Make sure your changes are tested (stories and/or unit, integration, or end-to-end tests)
• Make sure to add/update documentation regarding your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Maintainers

• If this PR should be tested against many or all sandboxes,
  make sure to add the ci:merged or ci:daily GH label to it.
• Make sure this PR contains one of the labels below.

["cleanup", "BREAKING CHANGE", "feature request", "bug", "documentation", "maintenance", "dependencies", "other"]

[shilman]

Also probably related #22110

[ndelangen]

I think this is the only significant change? the rest is more cleanup/linting?

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 1caa075. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 1 target

• nx run-many -t build -c production --parallel=3

---

Sent with 💌 from NxCloud.

[JReinhold]

I think this change looks good, GPT-4 conjured up the exact same string replacement, which obviously means this is pristine quality! 💅

[JReinhold]

Most likely also fixes #25114