[DO NOT MERGE] Allocating fixed size for upload chunk content

[Gautham-coder]

Issue

While #540 did resolve the memory leak for 64bit, the PR had this note
The current behavior is such that we don't see increase the memory till the chunk size is equal to or less than the one used initially. That is, it is advisable to use the same chunk size for all the chunks.

Proposed changes

This PR will be used to discuss the possibility of using a fixed size buffer irrespective of the content length, with this in the increase in memory is seen only initially. Varying content size causes no further increase. The Fixed memory size is set to 6MB for testing

This PR addresses Issue: zowe/zss#777

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Change in a documentation
• Refactor the code
• Chore, repository cleanup, updates the dependencies.
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

PR Checklist

Please delete options that are not relevant.

• If the changes in this PR are meant for the next release / mainline, this PR targets the "staging" branch.
• My code follows the style guidelines of this project (see: Contributing guideline)
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• New and existing unit tests pass locally with my changes
• video or image is included if visual changes are made
• Relevant update to CHANGELOG.md
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works, or describe a test method below

Testing

Upload chunks less than 6MB

Further comments

Needs discussion with the squad.
There are other places that process this chunk and allocate memory for ex

zowe-common-c/c/httpfileservice.c

Line 897 in 8a8a151

char *dataToWrite = safeMalloc(dataToWriteSize, "CONVERT BUFFER");

Start up:

Without fix the PRIVATE-64 value can be seen increasing to 1GB for large files.

With fix, after upload:

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud