Response body position change according to master

Type of change

• Bug Fix
• Feature

Please provide link to gitlab issue or ADR(Architecture Decision Record)

Does this introduce a change in the core logic?

• [YES/NO] NO

Does this introduce a change in the cloud provider implementation, if so which cloud?

• AWS
• Azure
• Google Cloud
• IBM

Does this introduce a breaking change?

• [YES/NO] No

What is the current behavior? moving response body according to the changes merged in master

What is the new/expected behavior?

Have you added/updated Unit Tests and Integration Tests?

Task ID: 32413 Green pipeline: https://community.opengroup.org/osdu/platform/system/notification/-/pipelines/229242

Any other useful information

drawback of not printing response body in send method: we loose on the response body of the createResource, create legal tags and delete legal tags, we can't print response body in send method because other service providers are printing response body in their respective test wherever needed by them and we can only call response body once

test case scenarios: green case: 4xx case: 5xx case: