Gracefully handle MARC records that exceed the size limit

Purpose/Overview:
In the current data export implementation when the record exceeds max allowed MARC record limit (99,999 characters) the export job crashes with the following error:

ExportManagerImpl Export is failed, cause: Record is too long to be a valid MARC binary record, it's length would be <projected size> which is more than 99999 bytes

and .mrc file is not generated at all.

The record might exceed the limit when the exported instance has thousands associated items and the export includes  SRS Bib and inventory holdings and items data.

Requirements/Scope:
If the record exceeds the MARC record length, then

• Record should not be exported
• The information about the record should be added to the user error log using the standard entry :

  <dateandtime> ERROR Record is too long to be a valid MARC binary record, it's length would be <projected record length> which is more than 99999 bytes
  {
  "Instance UUID": "<affected record uuid>"
  "Instance HRID": "<affected record hrid>"
  "Instance Title": "<title>"
  "Inventory record link": <link to the record>
  }
  

• Remaining records are exported

Approach:

Acceptance criteria:

• The export doesn't crash and error is handled gracefully
• Information about the affected record is recorded in the export job log
• Remaining records are
• Unit tests are written
• API tests are updated

Additional information:

• Bugfest example of a record with thousands items: https://bugfest-juniper.folio.ebsco.com/inventory/view/e5080758-086a-4435-9f3e-cf58ff30e55e?qindex=hrid&query=in539231&sort=title
• Example of export job entry logs: https://bugfest-juniper.folio.ebsco.com/data-export/log/c73cd2cf-20d9-45e4-984f-f5896824819c