UIREC-269, UIREC-279, UIREC-284: Number generator functionality

[EthanFreestone]

Purpose

This PR serves to act as an example implementation of the number generator components from ui-service-interaction.
The behaviour expressed in the listed JIRA tickets is quite complex, so this implementation brings in some of the more modular components from the @folio/service-interaction library and builds the functionality itself
https://folio-org.atlassian.net/browse/UIREC-269
https://folio-org.atlassian.net/browse/UIREC-279
https://folio-org.atlassian.net/browse/UIREC-284

This covers the setting of number generator configuration options in the receiving settings, as well as then making use of them in the "receive" table, as well as the "add piece" modal.

When number generator is enabled for at least one of the given fields, a button appears, leading to a modal which allows the selection of sequences for each of the 3 fields "Accession number", "Call number" and "Item barcode".

Approach

The settings configurator makes use of mod-config to store simple strings from which the code can then make decisions about what number generator options to display.

Once in the table, each row will display an "actions" column with a button tha opens the modal mentioned above. If a field is set to allow number generation, there will then be a number generator selector for that field, which when selected and "generate" is pushed will fill out the correct field with the generated number.

In addition there is the option "use accession number for call number" which will instead render a combined selector, and on generate will fill both fields out with the same generated number.

Pre-Merge Checklist

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

• [X ] 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
    This one is difficult to do, since the tests are failing on master for me. I have left these for the time being, pending discussions around handover of this code
  • [ X] Duplications on new code is 3% or less
  • [ X] There are no major code smells or security issues
• Does this introduce breaking changes?
  • [ X] If any API-related changes - okapi interfaces and permissions are reviewed/changed correspondingly
  • [X ] There are no breaking changes in this PR.

[github-actions]

Jest Unit Test Statistics

186 tests   - 40   185 ✔️  - 40   1m 33s ⏱️ - 1m 3s
  63 suites  -   7       0 💤  -   1 
    1 files   ±  0       1 ❌ +  1 

For more details on these failures, see this check.

Results for commit 18c5a94. ± Comparison against base commit 43b80c8.

♻️ 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 18c5a94. ± Comparison against base commit 43b80c8.

♻️ This comment has been updated with latest results.

[NikitaSedyx]

do not use mod-configuration, it's deprecated

[elsenhans]

https://folio-org.atlassian.net/browse/UIREC-279
https://folio-org.atlassian.net/browse/UIREC-284

Hello @NikitaSedyx and @EthanFreestone !
As the two tickets have been assigned to me, my question is where the data for the settings and the 3 fields 'barcode', 'accessionNumber' and 'callNumber' should be saved, since there is no mod-receiving available.
Can someone please tell me how this is intended?
See https://folio-org.atlassian.net/browse/UIREC-284

1. For the settings, I started working on this branch:
   master...UIREC-284-settings-for-number-generator
   But where should I save this data? Should I use mod-settings for the setting-values?

2. For assigning the barcode, accession number and call number in the receive all view and in add/edit piece modal in the Receiving App.
   Where should this data be saved?
   See https://folio-org.atlassian.net/browse/UIREC-279