fix(stark-core): add support for http 204 status code when persisting logs

[SuperITMan]

As Stark does not use returned body when persisting logs, there is no need to force the backend
to send a 201 status code. The 204 status code should be accepted when no content is received.

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/NationalBankBelgium/stark/blob/master/CONTRIBUTING.md#-commit-message-guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[X] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

When persisting logs, Stark does not use response body. For utility resources as logging, Stark should accept 204 http status code in response.

What is the new behavior?

Stark logging service accept http 204 "no content" status code.

Does this PR introduce a breaking change?

[ ] Yes
[X] No

Other information

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information