refactor(organization): leverage organization property for servingExperimentsAllowed

[lprovost-coveo]

The organization has a new property (non-optional) called configuration which contains the boolean property servingExperiementsAllowed

The goal is to start leveraging the new property from the org and the new endpoint that was created to update that property.

• Added the property to the organization definition
• (breaking change) Removed the old entrypoint for getExperimentalStatus
• Switched over the existing update call to leverage the new endpoint
• Change the default from false to true since we don't promote false.

Acceptance Criteria

• My changes are publicly available, documented, and deployed in production. (i.e. on Swagger)
• JSDoc annotates each property added in the exported interfaces
• The proposed changes are covered by unit tests
• Commits containing breaking changes a properly identified as such
• README.md is adjusted to reflect the proposed changes (if relevant)
• My merge commit message will be conventional (See Conventional Commit)

[mcnoreau12]

lgtm

[JTangCoveo]

LGTM

[github-actions]

🎉 This issue has been resolved in version 55.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀