chore: Update data format for platform API feature management

[smartdev58]

Description

Updated json data format for Platform API for account creation update API endpoints features flags to accept false values on each feature. #5717

Fixes # (issue)

Type of change

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

https://www.loom.com/share/b0d9452d556f41738924239cba080e92

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented on my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[voko3456]

@sojan-official @pranavrajs can you please merge this is enhancement for remaining feature flag

[sojan-official]

The new format looks good to me and seems more versatile.
Added a comment on the patch request. lets process to merge once that is resolved.

[smartdev58]

I am done with the requested changes.

[smartdev58]

The new format looks good to me and seems more versatile. Added a comment on the patch request. lets process to merge once that is resolved.

I am done with the changes in patch request test spec.

[sojan-official]

@smartdev58, thanks a lot for the changes. I have slightly refactored the logic so that the behaviour is consistent for creation and update. With this change, the currently enabled features in an account or features enabled through installation configuration are not affected unless the feature key is explicitly mentioned in features params.

Example: 
Account 1 -> already has inbox_management / channel_facebook enabled
Patch /accounts/1  { features: {  inbox_management: false, channel_email: true } 

Based on the initial PR -> after the patch account will only have: channel_email to be true; the previously enabled channel_facebook is also used to get overwritten.

With the current changes: the account will have both channel_email and channel_facebook enabled after the patch.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.