feat[auth-export-report]: remove the Linked bib fields column

[SvitlanaKovalova1]

Purpose

MODEXPW-619 Authority headings change report - Remove the Linked bib fields column

Approach

• request stats as before for a non-ECS tenant.
• request stats as before and set shared = true for the consortium Central tenant.

The getConsortiumAuthorityDataStat(int limit) method is responsible for reading authority update statistics from both the Member tenant and the Central tenant when the job runs in a consortium member context.
Flow for ECS Member tenant:

• fetch stats with the same parameters from both the consortium Central and Member tenants.
• if both collections contain data:
  - compares the metadata.startedAt timestamp of the first element in each list.
  - returns and removes the stat with the more recent startedAt value.
• if memberTenantStats collection is empty → loads the next page from the member tenant.
• if consortiumTenantStats collection is empty → loads the next page from the central tenant.
• if both collections are empty after loading attempts → returns null to signal end of stream.
• if only one collection contains data → returns and removes the first element from that collection.

Pre-Merge Checklist:

Before merging this PR, please go through the following list and take appropriate actions.

• Does this PR meet or exceed the expected quality standards?
  • Code coverage on new code is 80% or greater
  • Duplications on new code is 3% or less
  • Check logging
  • There are no major code smells or security issues
• Does this introduce breaking changes?
  • Were any API paths or methods changed, added or removed?
  • Were there any schema changes?
  • Did any of the interface versions change?
  • Were permissions changed, added, or removed?
  • Are there new interface dependencies?
  • There are no breaking changes in this PR.

If there are breaking changes, please STOP and consider the following:

• What other modules will these changes impact?
• Do JIRAs exist to update the impacted modules?
  • If not, please create them
  • Do they contain the appropriate level of detail? Which endpoints/schemas changed, etc.
  • Do they have all they appropriate links to blocked/related issues?
• Are the JIRAs under active development?
  • If not, contact the project's PO and make sure they're aware of the urgency.
• Do PRs exist for these changes?
  • If so, have they been approved?

Ideally all of the PRs involved in breaking changes would be merged in the same day to avoid breaking the folio-testing environment. Communication is paramount if that is to be achieved, especially as the number of intermodule and inter-team dependencies increase.

While it's helpful for reviewers to help identify potential problems, ensuring that it's safe to merge is ultimately the responsibility of the PR assignee.

[sonarqubecloud]

Quality Gate passed

Issues
3 New issues
0 Accepted issues

Measures
0 Security Hotspots
86.7% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud