Migration generator displays incorrect filenames for generated migrations

[sevenseacat]

Describe the bug

When generating migrations, the displayed filenames say they're in the _build/dev folder:

.: ~/P/b/t/tunez-starter : chapter-6 (82ef0c9) : 4:32pm :.
$ mix ash.codegen add_unique_album_names_per_artist
Compiling 1 file (.ex)
Getting extensions in current project...
Running codegen for AshPostgres.DataLayer...

Extension Migrations:
No extensions to install

Generating Tenant Migrations:

Generating Migrations:
* creating _build/dev/lib/tunez/priv/repo/migrations/20250101125618_add_unique_album_names_per_artist.exs
* creating _build/dev/lib/tunez/priv/resource_snapshots/repo/albums/20250101125618.json

Which they're not, they are actually in priv/ right where they're supposed to be.

I can even command+click on the filename in my iTerm2 and it'll open the right file in the right place, in VSCode!

I don't actually know what's going on here, it's super weird.

Expected behavior

The correct filename, eg. priv/repo/migrations/20250101125618_add_unique_album_names_per_artist.exs should be displayed for a generated migration.

** Runtime

• Elixir version 1.17.3
• Erlang version 27.1
• OS macOS Sequoia
• Ash version 3.4.49
• AshPostgres version 2.4.20

[zachdaniel]

How interesting...we switched to use an option which points us to the priv directory of the repo, which must be pointing us to the symlinked location in _build... will look into it