Migration adds invalid migration task when non-keyword export is present in the page script body

[taylorzane]

Describe the bug

When migrating routes using npx svelte-migrate routes, if a file that is being migrated contains the text export anywhere in the <script> body a @migration task: Add data prop error will be inserted. This is to be expected when it is used as a keyword, but it should not trigger if it is used for any other reason.

Reproduction

1. Create a SvelteKit project using 1.0.0-next.405 (or older) with the following contents:

<!-- src/routes/test.svelte -->
<div>
  <DataExport></DataExport>
</div>

<script>
  import DataExport from '$lib/data_export.svelte'
</script>

The contents of $lib/data_export.svelte is irrelevant, and technically doesn't even need to exist to reproduce.

2. Run npx svelte-migrate routes

Let me know if you want a reproduction repository. The issue seemed self-evident enough to not require one.

Logs

N/A

System Info

N/A

Severity

annoyance

Additional Information

No response