feat: new config property propagateErrors

[AleksandrRogov]

Introducing a new global config option propagateErrors.

This option is related to a raised issue #203 where you can find more information behind this change. Main things that will need to be noted here is the following:

• This option is temporary. Meaning, it will be available until the next major version and will be removed then.
• This option is introduced to standardize the behavior of all requests and it is recommended that you set it to true in all new projects using DynamicsWebApi so all requests have expected behaivor. Usage of propagateErrors is optional.
• For existing projects, if you set propagateErrors to true - watch out for the following operations: update, upsert and deleteRecord. Those requests will now throw errors instead of handling 412 and 404 errors.

Example:

const dynamicsWebApi = new DynamicsWebApi({
    serverUrl: "https://myorg.api.crm.dynamics.com",
    onTokenRefresh: acquireToken,
    propagateErrors: true
});

// the following will now throw an error if a contact with <KEY> exists instead of returning "false"
await dynamicsWebApi.update({
    collection: "contacts",
    key: "<KEY>",
    data: { firstname: "John" }
});

⚠️ Deprecation Notice

Error handling of 404 and 412 errors is now treated as legacy and will be removed in update, upsert and deleteRecord operations to standardize the request behavior.

[coveralls]

coverage: 98.767% (+0.4%) from 98.334% — feature/propagate-errors-config-options into dev