Update cypress functional tests to cover all currently used v1-v4 APIs - both success and error paths

[lukaszgryglicki]

Update cypress functional tests:

• Some tests are failing: some fail due to hardcoded values that are expected to be present in dev (but aren't) and possibly some missing permissions on X-ACL/Auth0 tokens (for test user that is sued for tests).
• Add testing for errors (like parameter validation errors) in the existing V4 APIs covergae.
• Add missing V4 APIs coverage (with both happy path and errors like above).
• Add v1/v2/v3 APIs coverage (with both happy path and errors like above).
• Do this for all APIs that are identified as being used since I've deployed API calls logging for v1/v2/v3/v4 (21/8/25 about 5 AM UTC).

[lukaszgryglicki]

API logging was added 2025-08-21 04:33 AM UTC I'm now fetching API stats to figure out which APIs are actually used in prod.

[lukaszgryglicki]

Those are prod APIs that are currently in use (aggregated from 7 days and 2 hours of usage):

      N API path
 279784 /v2/github/activity
  20305 /v4/ops/health
  20220 /v3/ops/health
   1909 /v2/repository-provider/github/sign/<id>/<id>/<id>
   1009 /v2/project/<uuid>
    837 /v2/user/<uuid>
    634 /v4/company/<sfid>/project/<sfid>/cla
    372 /v4/company/<uuid>/project/<sfid>/events
    358 /v2/github/installation
    331 /v3/organization/search
    258 /v4/project/enabled/<sfid>
    228 /v4/metrics/total-count
    215 /v4/company/<uuid>/project/<sfid>/cla-managers
    214 /v2/user/<uuid>/active-signature
    200 /v4/request-individual-signature
    181 /v4/signatures/project/<sfid>/company/<uuid>
    168 /v2/return-url/<uuid>
    154 /v4/signed/individual/<id>/<id>/<id>
    151 /v4/foundation/<lfxid>/cla-groups
    145 /v2/check-prepare-employee-signature
    144 /v4/company/<uuid>/project/<sfid>/contributors
    137 /v4/github/activity
    134 /v3/company/external/<sfid>
    128 /v4/company/<sfid>/project/<lfxid>/cla
    121 /v4/foundation-mapping
    106 /v4/company/external/<sfid>
    103 /v4/company/<uuid>/project/<sfid>/active-cla-list
     89 /v2/request-employee-signature
     85 /v4/cla/authorization
     67 /v4/template
     63 /v4/project/<lfxid>/github/organizations
     47 /v4/company/<uuid>/project/<lfxid>/events
     45 /v4/foundation/<sfid>/cla-groups
     44 /v4/events/project/<lfxid>
     44 /v*/swagger
     35 /v4/signatures/project/<lfxid>/company/<uuid>
     32 /v4/signatures/project/<uuid>
     30 /v4/signatures/project/<sfid>/company/<uuid>/clagroup/<uuid>/approval-list
     30 /v4/company/<lfxid>/project/<sfid>/cla
     29 /v4/company/<uuid>/cla-group/<uuid>/cla-managers
     26 /v4/template/<uuid>/preview
     26 /v4/cla-group/<uuid>/icla/signatures
     25 /v3/signatures/<uuid>/<uuid>/icla/pdf
     24 /v4/notify-cla-managers
     22 /v4/company/<uuid>/project/<lfxid>/cla-managers
     21 /v4/company/<uuid>/project/<lfxid>/contributors
     19 /v2/project/<null>
     15 /v4/events/project/<sfid>
     14 /v4/company/<sfid>/admin
     13 /v4/request-corporate-signature
     13 /v4/cla-group/validate
     13 /v2/gerrit/<uuid>/corporate/agreementUrl.html
     12 /v4/company/<uuid>/project/<sfid>/cla-manager
     11 /v3/company/external/<lfxid>
     10 /v4/events/foundation/<sfid>
     10 /v1/user/gerrit
      9 /v4/cla-group/<uuid>/corporate-contributors
      8 /v4/user/<uuid>/invite-company-admin
      8 /v4/project/<sfid>/github/organizations
      8 /v4/company/<uuid>/claGroup/<uuid>/cla-manager-designee
      8 /v2/user/<uuid>/project/<uuid>/last-signature
      8 /v*/api-docs
      7 /v4/company/<lfxid>/admin
      5 /v4/signed/corporate/<uuid>/<uuid>
      5 /v4/company/external/<lfxid>
      5 /v4/cla-group/<uuid>/project/<lfxid>/gerrits
      5 /v3/signatures/company/<uuid>
      5 /v2/health
      4 /v4/signatures/project/<lfxid>/company/<uuid>/clagroup/<uuid>/approval-list
      4 /v4/project/<lfxid>/gitlab/organizations
      4 /v4/company/lookup
      4 /v4/company/<uuid>/project/<sfid>/cla-manager-designee
      3 /v4/signatures/company/<uuid>/clagroup/<uuid>/ecla-auto-create
      3 /v4/signatures/<uuid>/signed-document
      3 /v4/company/<uuid>/project/<lfxid>/cla-manager
      3 /v4/company/<sfid>/user/qonto/claGroupID/<uuid>/is-cla-manager-designee
      3 /v3/users/username/<name>
      3 /v3/company/user/<uuid>/invites
      2 /v4/user/<uuid>/company
      2 /v4/template/preview
      2 /v4/company/name/<name>
      2 /v4/company/<uuid>/project/<lfxid>/cla-manager-designee
      2 /v4/company/<sfid>/user/<name>/claGroupID/<uuid>/is-cla-manager-designee
      1 /v4/signatures/company/<uuid>/clagroup/undefined/ecla-auto-create
      1 /v4/project/<lfxid>/github/repositories
      1 /v4/project/<lfxid>/github/organizations/<name>/config
      1 /v4/cla-group/<uuid>
      1 /v4/cla-group
      1 /v3/ops/version
      1 /v3/company/<uuid>/cla/invitelist
      1 /v3/company
      1 /v2/company/<uuid>
      1 /v1/company

Next I will figure out which of them are covered in cypress functional tests and which aren't using AI for this as requested @mlehotskylf .

[lukaszgryglicki]

PR up: #4775 (this generated the above stats).

[lukaszgryglicki]

AI update:

✅ Answer: Cypress functional tests cover roughly 30–35% of the distinct API endpoints you see in production, but only ~5–10% of total API traffic volume because the most frequently called v2 endpoints (like /v2/github/activity) are not exercised in Cypress.

[lukaszgryglicki]

I will start from fixing errors in already existing test coverage.

[lukaszgryglicki]

1st PR up: #4779.