Fix Prisma migrate file format #16547
                
     Merged
            
            
          
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Summary
When using PowerShell on Windows, the command in the docs to generate a migration file produces a file in UTF-16 format which wrangler is unable to migrate properly.
Updating the command to use the output flag instead produces a file in UTF-8 which runs fine with the migrate command
Solution found in: prisma/prisma#23702
Prisma release with the fix: https://github.com/prisma/prisma/releases/tag/5.12.1
Screenshots (optional)
Error produced when file is in UTF-16