feat: update to spago@next

[srghma]

Description of the change

update to spago@next

locally tests dont work, but on ci - work

---

Checklist:

• Added the change to the changelog's "Unreleased" section with a link to this PR and your username
• Linked any existing issues or proposals that this pull request should close
• Updated or added relevant documentation in the README and/or documentation directory
• Added a test for the contribution (if applicable)

[natefaubion]

I believe latest spago has landed on camelCase fields instead snake_case, FWIW.

[srghma]

I believe latest spago has landed on camelCase fields instead snake_case, FWIW.

again update everything

sd -s "packageSet" "package_set" $(fd --type file -e yaml -e yml -e purs)
sd -s "extraPackages" "extra_packages" $(fd --type file -e yaml -e yml -e purs)
# or 
spago build --migrate ?

NB: not yet published to npm

[thomashoneyman]

Looks like the spago in CI is old? And — we don’t need psa anymore if we use the new spago, it’s bundled in.