fix(request-termination) allow null value for body or message

[shashiranjan84]

Summary

Allow user to unset either message or body.

Full changelog

• update schema self_check to support null value for message or body
• add relevant spec

[thibaultcha]

In the next branch, we already ported plugins to the new DAO, and we currently are in the process of convert plugins schemas to the new schema library (#3778). The new schema library/Admin API endpoints should support JSON null un-setting out of the box. Still, it is nice to have tests for this.

1. We should probably wait until Feat/plugins schemas to new db #3778 is done, before reworking this PR to reflect the desired changes, and introduce those new tests
2. There should be a test that makes two subsequent requests, the first one un-setting message, and the second one un-setting body). That should not be possible (as per the "either one of message or body should be set" error).

[thibaultcha]

"WIP" label applied to reflect the need for #3778 to be merged first, before porting those changes to the new schema. Keeping the PR open in the meantime!

[shashiranjan84]

There should be a test that makes two subsequent requests, the first one un-setting message, and the second one un-setting body). That should not be possible (as per the "either one of message or body should be set" error).

good catch, wondering if it possible to figure out what plugin state saved in DB from self check?

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Shashi Ranjan seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}