refactor!: make Content initialisers take nplike, parameters as keyword

[agoose77]

---

📚 The documentation for this PR will be available at https://awkward-array.readthedocs.io/en/agoose77-refactor-content-keyword/ once Read the Docs has finished building 🔨

[codecov]

Codecov Report

Merging #1921 (b3cd399) into main (4035aca) will decrease coverage by 0.00%.
The diff coverage is 91.46%.

Additional details and impacted files

Impacted Files	Coverage Δ
src/awkward/_broadcasting.py	93.38% <ø> (ø)
src/awkward/_connect/pyarrow.py	88.46% <ø> (ø)
src/awkward/_util.py	82.46% <ø> (ø)
src/awkward/contents/bitmaskedarray.py	65.00% <ø> (ø)
src/awkward/forms/bitmaskedform.py	86.07% <ø> (ø)
src/awkward/forms/bytemaskedform.py	86.30% <ø> (ø)
src/awkward/forms/indexedform.py	89.61% <ø> (ø)
src/awkward/forms/indexedoptionform.py	93.15% <ø> (ø)
src/awkward/forms/listform.py	82.71% <ø> (ø)
src/awkward/forms/recordform.py	88.57% <ø> (ø)
... and 33 more

[jpivarski]

Yes, but also for Forms and Types, since there's a strong symmetry between these and Contents (especially Forms).

I'll get started on that, adding to this PR, if that's alright.

[agoose77]

Fab, thanks for making this change. I was tempted to do them in multiple PRs, but on second thought it's less churn to do it all now. I didn't give it too much thought as I was playing around with semgrep to actually generate this PR

You can see the config that I used to do these renames, run with

semgrep -a --config=./rename.yaml

rename.yaml

rules:
- id: single-arg
  patterns:
    - pattern: '$F($X, $Y, $Z, $Q, $W, $U)'
    - metavariable-regex:
        metavariable: $F
        regex: ^.*ListArray$
  languages: [python]
  severity: WARNING
  message: Semgrep found a match
  fix: $F($X, $Y, $Z, $Q, $W, parameters=$U)

It wasn't perfect; sometimes it mangled the source. But careful staging worked well.

[jpivarski]

We were thinking along the same lines: I wanted to make them separate commits, rather than separate PRs, so that they can be checked in stages. It's just a question of what granularity the main branch should have. (After this refactoring is done, it's unlikely someone will want to see them separately, and if they do, they can follow the merge commit to this PR and see the individual commits.)

[agoose77]

I ran a check over the forms with

rules:
- id: single-arg
  patterns:
    - pattern: '$F(...)'
    - pattern-not: '$F(..., parameters=$X)'
    - metavariable-regex:
        metavariable: $F
        regex: ^.*Type$
  languages: [python]
  severity: WARNING
  message: Semgrep found a match

and visually ensured the correct results