refactor: move optional arguments of bipartite-degseq functions behind the ellipsis

[krlmlr]

Part of the repo-wide ellipsis migration coordinated in #2757 —
see that PR for the full rationale (CONTRIBUTING.md, Argument Order and the Ellipsis).
Based directly on main (the registry split landed via #2779); a single topic commit.

What this does

Inserts ... between the defining arguments (head) and the optional
modifiers (tail) of 2 exported bipartite-degseq functions.
Arguments after ... become keyword-only.

• Legacy positional or abbreviated calls are recovered by the generated
  ARG_HANDLE block and emit a single lifecycle::deprecate_soft("3.0.0", …) —
  behavior is unchanged.
• No defaults change, no arguments are renamed, deprecated functions untouched.
• Registry: tools/migrations/bipartite-degseq.R; blocks regenerated via
  Rscript tools/generate-migrations.R (idempotent, CI-checked).
• Rd usage/arguments updated mechanically (see note below).

New signatures

function	head (positional)	keyword-only tail
bipartite_projection()	graph, types	multiplicity, probe1, which, remove.type
is_graphical()	out.deg, in.deg	allowed.edge.types

Notes for review

• The environment used to prepare this PR cannot install igraph.r2cdocs
  (GitHub API unreachable), so man/*.Rd files were updated mechanically
  (usage + ... argument item) instead of via devtools::document().
  R CMD check's usage↔formals validation passes; a follow-up
  devtools::document() run may reflow whitespace but should produce no
  semantic diff.
• Package tests that called these functions positionally were updated to
  named arguments (they are the same soft-deprecation user code will see).