UIBULKED-571 Errors in response to UI calls

[vashjs]

Based on the new requirements, for all non bulk-operation modules to which the UI makes requests, errors should be generated according to the following template:

<module-name> returns status code: <status-code> - <error details>.

Since some models do not have a message and the message consists only of a status code, additional logic has been added for such cases. Depending on the specific case, a basic HTTP error will be shown based on the pre-created dictionary.

Refs: UIBULKED-571

[github-actions]

Jest Unit Test Statistics

    1 files  ±0    47 suites  ±0   3m 7s ⏱️ +2s
306 tests +6  306 ✔️ +6  0 💤 ±0  0 ❌ ±0 
312 runs  +6  312 ✔️ +6  0 💤 ±0  0 ❌ ±0 

Results for commit 6432548. ± Comparison against base commit 7db3438.

♻️ 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 6432548. ± Comparison against base commit 7db3438.

♻️ This comment has been updated with latest results.

[sonarqubecloud]

Quality Gate failed

Failed conditions
78.9% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

[vashjs]

@folio-org/fe-tl-reviewers please review

[JohnC-80]

We can do better than the static lists contained in this - HTTP codes/messages or UI module names... as the capabilities of bulk-edit increase, the static list of module names would have to be updated. Blocking until further PO feedback is obtained.

[JohnC-80]

A static npm library is better than keeping the code : message mapping in our own code, but only just so. If this information is intended for developers to fix the issue, a lack of an error response from the server is most definitely an issue - but that isn't helped if an error message is contrived by the UI. UI modules should not make up for the shortcomings of backend modules.
FOLIO generally keeps a separation between the UI and the backend via interface - this said, backend modules can change without the UI caring, so long as the same interface is still provided. Now with the static list in place, the UI for Bulk Edit has to concern itself with potential changes. Future developments will see if we can make this functionality more dynamic... until then, here we are.

See my comment for the architectural issues in this approach. I can only ask for these aspects of this work to be reconsidered.