Improve schema import error propagation

[akshay05n]

imodel-native: iTwin/imodel-native#749

[mergify]

This pull request is now in conflicts. Could you fix it @akshay05n? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

[pmconne]

Pending @khanaffan's approval.

[pmconne]

Integration test failure:

  1) Schema synchronization
       import schema acquire schema lock when need to transform data:
     Error: Failed to throw error with message: "exclusive lock is already held"
      at assertThrowsAsync (src/integration/SchemaSync.test.ts:108:9)
      at processTicksAndRejections (node:internal/process/task_queues:95:5)
      at Context.<anonymous> (src/integration/SchemaSync.test.ts:930:5)

[akshay05n]

Integration test failure:

  1) Schema synchronization
       import schema acquire schema lock when need to transform data:
     Error: Failed to throw error with message: "exclusive lock is already held"
      at assertThrowsAsync (src/integration/SchemaSync.test.ts:108:9)
      at processTicksAndRejections (node:internal/process/task_queues:95:5)
      at Context.<anonymous> (src/integration/SchemaSync.test.ts:930:5)

This is due to the change in importSchemas and importXmlSchemas APIs. The integration test will pass again once the native changes are merged and the new @bentley/imodeljs-native package is released.

[pmconne]

@tcobbs-bentley @toddsouthenbentley @wgoehrig @aruniverse @calebmshafer your review is required.

[pmconne]

/azp run iTwin.js

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[pmconne]

/azp run iTwin.js Docs - YAML

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[pmconne]

/azp run iTwin.js Integration - GitHub

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[pmconne]

@DanRod1999 any theories as to why the builds did not trigger when the addon was merged?

[DanRod1999]

I will take a closer look. But it might just be a fluke on GitHub. I've seen pipelines not trigger before, but will investigate to make sure it is not a problem in our side