update purescript-parallel to last version in bower.json

[srghma]

Description of the change

I was doing spago publish on

and got weird error

 ~/projects/purescript-open-mkdirp-aff $ spago publish
Reading Spago workspace configuration...

✅ Selecting package to build: open-mkdirp-aff

Downloading dependencies...
Building...
           Src   Lib   All
Warnings     0     0     0
Errors       0     0     0

✅ Build succeeded.

Passed preliminary checks.
Pushing tag 'v1.2.0' to the remote
Building again with the build plan from the solver...
Building...
purs compile: No files found using pattern: .spago/p/parallel-6.0.0/src/**/*.purs
[1/3 ModuleNotFound] .spago/p/aff-7.1.0/src/Effect/Aff.purs:45:1

  45  import Control.Parallel (parSequence_, parallel)
      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  Module Control.Parallel was not found.
  Make sure the source file exists, and that it has been provided as an input to the compiler.

[2/3 ModuleNotFound] .spago/p/aff-7.1.0/src/Effect/Aff.purs:46:1

  46  import Control.Parallel.Class (class Parallel)
      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  Module Control.Parallel.Class was not found.
  Make sure the source file exists, and that it has been provided as an input to the compiler.

[3/3 ModuleNotFound] .spago/p/aff-7.1.0/src/Effect/Aff.purs:47:1

  47  import Control.Parallel.Class (sequential, parallel) as Exports
      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  Module Control.Parallel.Class was not found.
  Make sure the source file exists, and that it has been provided as an input to the compiler.

           Src   Lib   All
Warnings     0     0     0
Errors       0     3     3

❌ Failed to build.

its bc .spago/p/parallel-6.0.0/ didnt exist

so I cp .spago/p/parallel-7.0.0/ .spago/p/parallel-6.0.0/ and problem went away

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)