ci(DA): restrict concurrency to avoid failures in tests

[Jolg42]

We might be able to remove the restriction if we rework the tests.

To simplify: concurrency happens when 2 of the following happen: PR is open / merged or the update checked finds a new dev / latest / integration version.

Example failure:
https://github.com/prisma/ecosystem-tests/actions/runs/9287611832/job/25557871027?pr=5005#step:8:154

> turso-vercel-nextjs-edgemw@ test /home/runner/work/ecosystem-tests/ecosystem-tests/driver-adapters-wasm/turso-vercel-nextjs-edgemw
> jest index.test.js

FAIL ./index.test.js (10.28 s)
  ✕ prisma version and output (9954 ms)

  ● prisma version and output

    expect(received).toEqual(expected) // deep equality

    - Expected  - 1
    + Received  + 5

      Object {
    -   "error": "Transaction API error: Transaction already closed: Could not perform operation.",
    +   "error": "
    + Invalid `prisma.user.createMany()` invocation:
    +
    +
    + SQLITE_CONSTRAINT: SQLite error: UNIQUE constraint failed: User.email",
      }

[Jolg42]

Another example
https://github.com/prisma/ecosystem-tests/actions/runs/9286333431/job/25555841669#step:8:247

    +   "error": "
    + Invalid `prisma.user.update()` invocation:
    +
    +
    + An operation failed because it depends on one or more records that were required but not found. Record to update not found.",
      }