feat(CRater): Allow requests to be sent to Berkeley endpoint

[Aaron-Detre]

Changes

• Added method forBerkeleyEndpoint() to CRaterRequest interface which checks for "berkeley_" prefix.
• Exposed cRaterUrl setter in CRaterRequest interface to enable new method setRequestCRaterUrl in CRaterService to set the cRaterUrl for any implementation of CRaterRequest rather than writing duplicate code for each implementation of CRaterRequest.
• Added tests to make sure that getScoringRequest() and getVerificationRequest() in CRaterService are trying to send HTTP requests to the Berkeley endpoint rather than the ETS endpoint when the request's itemId has the "berkeley_" prefix.

Test

• Make sure scoring and verification requests without the "berkeley_" prefix in the itemId are still sent to the ETS endpoint.
  • The dialog guidance should still work as normal since none of the current itemId's should have the "berkeley_" prefix.
• Make sure scoring and verification requests with the "berkeley_" prefix in the itemId are sent to the Berkeley endpoint once it exists.

Closes #286

[hirokiterashima]

Good start.

We'll also need to allow WISE admins to specify values for "berkeley_cRater_client_id" and "berkeley_cRater_password" keys. These will be used to authorize access to the Berkeley endpoint.

[hirokiterashima]

LGTM

[hirokiterashima]

🎉 This PR is included in version 1.6.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀