Description

See FINERACT-2335.

It's so we get this:

$ ls -lh fineract-war/build/distributions/
total 433M
-rw-rw-r-- 1 marie users 422M Jul 28 07:11 apache-fineract-bin-1.12.1.tar.gz
-rw-rw-r-- 1 marie users  11M Jul 28 07:06 apache-fineract-src-1.12.1.tar.gz

instead of this:

$ ls -lh fineract-war/build/distributions/
total 433M
-rw-rw-r-- 1 marie users 422M Jul 28 07:11 apache-fineract-1.12.1-binary.tar.gz
-rw-rw-r-- 1 marie users  11M Jul 28 07:06 apache-fineract-1.12.1-src.tar.gz

and so their contents match their names (so they explode into a directory of the same name as the file, minus .tar.gz)

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.