FINERACT-2326: add test Fineract API requests to README

[kengneruphine]

Description

Update the Readme file by including the headers (tenantid and credentials) to facilitate new contributors in testing the application on Fineract.

FINERACT-2326

Checklist

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

• Write the commit message as per https://github.com/apache/fineract/#pull-requests
• 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 coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/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
• Submission is not a "code dump". (Large changes can be made "in repository" via a branch. Ask on the developer mailing list for guidance, if required.)

FYI our guidelines for code reviews are at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide.

[kengneruphine]

@adamsaghy could you please review this PR? Thank you

[meonkeys]

I can... I've been editing docs a bunch lately.

[meonkeys]

Thanks for your patch, @kengneruphine !

Please also review https://github.com/apache/fineract#pull-requests ... you need to create a JIRA ticket. Every Apache Fineract GitHub PR has an associated JIRA ticket and follows a naming convention. If you only change a few lines in the top-level readme I might still approve your patch, but it's just good practice to always create JIRA tickets and follow the PR naming convention.

[steinwinde]

Maybe beyond the scope of the PR, but for my opinion the most important point missing in the current README is any information regarding hardware requirements (minimum memory in GB etc.). Based on my conversations with newcomers this (and not anything software related) is the biggest impediment when starting out with Fineract.

[adamsaghy]

Thanks for your patch, @kengneruphine !

Please also review https://github.com/apache/fineract#pull-requests ... you need to create a JIRA ticket. Every Apache Fineract GitHub PR has an associated JIRA ticket and follows a naming convention. If you only change a few lines in the top-level readme I might still approve your patch, but it's just good practice to always create JIRA tickets and follow the PR naming convention.

You can use FINERACT-2326 for this ;)

[meonkeys]

Maybe beyond the scope of the PR, but for my opinion the most important point missing in the current README is any information regarding hardware requirements (minimum memory in GB etc.). Based on my conversations with newcomers this (and not anything software related) is the biggest impediment when starting out with Fineract.

Good to know, thanks @steinwinde . Maybe a separate PR for that, though, unless you and @kengneruphine want to expand work in this PR? Your call

superseded by latest changes, will start new review

[meonkeys]

Please review and update your patch.

[meonkeys]

@kengneruphine LGTM. Please squash this PR into a single commit and rebase on develop, then I'll fast-forward merge it. We don't need to wait for the checks to finish since this PR only touches the README.