#179 Consistently use URI object in APIs

[ndoschek]

Consistently use URI object in APIs

• Update to latest modelserver-client version
• Use urijs as typed URI library
  • Use URI objects in APIs and internally for proper URI handling
  • Adapt interfaces, tests, custom examples

General

• Remove simple-import-sort eslint plugin as it interferes with the built-in import sort
• Add script to upgrade emfcloud dependencies

Part of eclipse-emfcloud/emfcloud#179

Contributed on behalf of STMicroelectronics

---

Testing:

• Use the existing unit and integration tests
• Use the custom-*-example implementations to test custom commands, routing etc.

[cdamus]

Looks great! I have a few comments in-line, but more significantly there are changes needed in the server-integration-test.spec.ts file. I'm perplexed as to why the tests seem to run correctly (when giving them the Java server instance that they need for complete execution).

At lines 47 and 169 of server-integration-test.spec.ts I get compilation errors on a string argument that is now expected to be an URI object. I don't understand why the tests work. I see that in most places in this file the string arguments were previously replaced with URIs, so I think we should finish the job here.

[ndoschek]

Thanks @cdamus for your review, I added another commit that addresses your comments.
I am also confused why the compilation didn't show for me on the first cycle, but now I hopefully catched all occurrences of outdated string-uris.

[cdamus]

The new makeUrl(...) change breaks transaction endpoint URLs as shown by test failures. Unfortunately, the build doesn't catch that because all of the transaction-related tests require the Java server and so are skipped in the build, sorry.

[cdamus]

LGTM! Thanks.