feat: expose ORT report-formats workflow input

[MykhailoRyzhman]

Applicable issues

• fixes #

Description of changes

Expose ort-report-formats as a workflow input across all reusable workflows that run ORT.

Consumer repositories currently cannot control which ORT reporters are generated. The default set (CycloneDx, SpdxDocument, WebApp) is hardcoded in oss-review-toolkit/ort-ci-github-action and always passed implicitly. This is a problem when the WebApp reporter fails with OutOfMemoryError: Java heap space on CI (ORT JVM heap is capped at 5 GiB in the action), while CycloneDX and SPDX reports are sufficient for compliance.

This change adds ort-report-formats to:

• node_pr.yml, node_release.yml, node_test.yml
• java_pr.yml, java_release.yml, java_test.yml
• python_docker_pr.yml, python_docker_release.yml, python_docker_test.yml
• python_package_pr.yml, python_package_release.yml, python_package_test.yml
• generic_docker_pr.yml, generic_docker_release.yml, generic_docker_test.yml

The input is forwarded to ort-ci-github-action as report-formats. Default value is unchanged: CycloneDx,SpdxDocument,WebApp.

Example for a consumer repository that needs to skip the WebApp report:

jobs:
  run_tests:
    uses: epam/ai-dial-ci/.github/workflows/node_pr.yml@<version>
    with:
      ort-report-formats: "CycloneDx,SpdxDocument"
    secrets: inherit

Checklist

• custom check

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.