UIORGS-356 - Show in version history record view, which fields have been edited

[usavkov-epam]

Purpose

https://folio-org.atlassian.net/browse/UIORGS-356

Give the user the ability to access the change log that displays all edits that have been made to the record.

Approach

Apply ACQ approach to display version history (ui-orders app is a prototype).

Prepare organization components views adapted for version history context. Implement a hook, that will aggregate version history data for specific versions.

Screenshot

chrome_xqm4fomDmQ.mp4

Pre-Merge Checklist

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

• I've added appropriate record to the CHANGELOG.md
• 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
  • There are no major code smells or security issues
• Does this introduce breaking changes?
  • If any API-related changes - okapi interfaces and permissions are reviewed/changed correspondingly
  • 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.

[github-actions]

Jest Unit Test Statistics

    1 files  ±0    89 suites  +3   2m 54s ⏱️ +9s
280 tests +4  278 ✔️ +5  2 💤 ±0  0 ❌  - 1 
284 runs  +4  281 ✔️ +5  3 💤 ±0  0 ❌  - 1 

Results for commit c1569f8. ± Comparison against base commit 9a29cc4.

♻️ This comment has been updated with latest results.

[github-actions]

BigTest Unit Test Statistics

0 tests  ±0   0 ✔️ ±0   0s ⏱️ ±0s
0 suites ±0   0 💤 ±0 
0 files   ±0   0 ❌ ±0 

Results for commit c1569f8. ± Comparison against base commit 9a29cc4.

♻️ This comment has been updated with latest results.

[SerhiiNosko]

Great and huge work done here

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

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

See analysis details on SonarQube Cloud