CORTX-33819: Updating code owners

[pankajgborole]

Problem Statement

• Problem statement

Design

• For Bug describe the fix here.
• For Feature, Post the link to the solution page on the confluence CORTX Foundation Library

Coding

• Coding conventions are followed and code is consistent [Y/N]:
• Confirm All CODACY errors are resolved [Y/N]:

Testing

• Are test cases updated along with code changes due to Enhancements/Bugs [Y/N]:
• Confirm that new test cases are added to regression and sanity plan files and relevant feature plan files [Y/N]:
• Confirm that Test Cases are added for new features added [Y/N]:
• Confirm Test Cases cover Happy Path, Non-Happy Path and Scalability [Y/N]:
• Confirm Testing was performed with installed RPM/K8s deployment [Y/N]:

Review Checklist

Before posting the PR please ensure:

• PR is self reviewed
• Is there a change in filename/package/module or signature [Y/N]:
• If yes for above point, Is a notification sent to all other cortx components [Y/N]
• New package/s added to setup.py?
• Jira is updated
• Check if the description is clear and explained.
• Check Acceptance Criterion is defined.
• All the tests performed should be mentioned before Resolving a JIRA.
• Verification needs to be done before marked as Closed/Verified.

KVstore/Confstore feature (changes/fixes) checklist

Confirm changes are made for:

• ConfStore
• KVStore
• ConfCli
• Test cases added for all above 3
• changes done in all the KVpayloads (ConsulKvPayload, IniKvPayload, KvPayload)

Documentation

• Changes done to WIKI / Confluence page

[welcome]

Thanks for your contribution in opening this pull request! Now you can be rewarded with a CORTX sticker by requesting cortx sticker
In the meantime, please check out the contributing guidelines and explore other ways you can get involved.

[sachinpunadikar]

+1

[welcome]

Thanks for your contribution to CORTX! 🎉