docs(findings): move or copy findings to another test

[Jino-T]

[sc-14815]

Description

Documents moving and copying findings to another test in DefectDojo Pro. The test can be in the same engagement, another engagement, or another asset.

• PRO__bulk_edit_findings.md: the new Move or Copy section of Bulk Edit:
  • how to pick the destination, including create-matching-engagement-and-test;
  • what a move changes (endpoints, finding group, risk acceptance, SLA, deduplication, note), and that a linked Jira issue stays linked;
  • what a copy carries, the risk-acceptance and deduplication rules for copies, and that an attachment whose stored file is missing is skipped and listed;
  • the permissions: the destination is checked before anything moves, and Bulk Edit needs edit permission on every selected finding, so a view-only user copies from the finding menu;
  • the public /api/v2/ move and copy actions for automation, with request examples, the 1,000-ID limit on bulk requests, and how unknown IDs are reported;
  • where to move or copy a single finding: Move or Copy Finding in its menu.
• PRO__findings.md: the Copy Finding menu entry becomes Move or Copy Finding. It offers the same toggle and destination as Bulk Edit, and offers Move only to users who can edit the finding.
• editing_findings.md: the note on the read-only Test field now points to Move or Copy Finding. It also says that changing test in an API update of a finding has no effect, so automations should use the move endpoint.

Documentation only; no code changes.