FINERACT-2607: Add missing 'status' enum values for command processin…

[Hysnijee]

Description

These values were never persisted on new migration files; they existed on old migrations.
Additionally I also return the enum_value instead of enum_message_property since it's more readable and it will look better on the UI.

Checklist

Please make sure these boxes are checked before submitting your pull request - thanks!

• Write the commit message as per our guidelines
• Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.
• Create/update unit or integration tests for verifying the changes made.
• Follow our coding conventions.
• Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/legacy-docs/apiLive.htm with details of any API changes
• This PR must not be a "code dump". Large changes can be made in a branch, with assistance. Ask for help on the developer mailing list.

Your assigned reviewer(s) will follow our guidelines for code reviews.

[Kengne-yvana]

@Hysnijee please sign your commit and write a test for this

[Hysnijee]

@Hysnijee please sign your commit and write a test for this

Verified the commits and adapted the integrationt test to assert this change on 480285f

[Aman-Mittal]

@Hysnijee @Kengne-yvana Has this discussed in Dev List Before?

[Hysnijee]

@Hysnijee @Kengne-yvana Has this discussed in Dev List Before?

I am a new contributor, this is my first time. But I didn't see this being mentioned anywhere on Jira besides the issue that I created

[Aman-Mittal]

@Hysnijee @Kengne-yvana Has this discussed in Dev List Before?

I am a new contributor, this is my first time. But I didn't see this being mentioned anywhere on Jira besides the issue that I created

Fair point, I recommend you to subscribe to the fineract dev list, From what i am seeing you are changing schema values. When you are doing changes in existing based on functionality related changed. These needs to be discussed first.

[Hysnijee]

@Hysnijee @Kengne-yvana Has this discussed in Dev List Before?

I am a new contributor, this is my first time. But I didn't see this being mentioned anywhere on Jira besides the issue that I created

Fair point, I recommend you to subscribe to the fineract dev list, From what i am seeing you are changing schema values. When you are doing changes in existing based on functionality related changed. These needs to be discussed first.

Thank you! I created a discussion in https://lists.apache.org/thread/fdm8c4ko68xvf593r0ofsrj2ks3tpvkf