Introduce task make target that runs tests before committing the provided message

[Kostov6]

What this PR does / why we need it:
Inspired by Use git tactically this PR introduces make task m="commit message" that ensures the code compiles and runs tests before committing all the added files with the given commit message. These are the biggest benefits from make task:

• There are no commits that represent a partial functionality state. So when going over commits the reviewer doesn't need to keep mental track of previous partial states. That way all he needs to focus on is whether the current commit does what is described to do from the commit message
• This encourages people to split big tasks into smaller subtasks that are achievable and reviewable
• This discourages doing huge tasks that don't seem to be achievable through incremental steps (avoiding sunk cost fallacy)

This PR's commit is added using make task

$  make task m="Introduce task make target that runs tests before commiting the provided message"
-------------
Staged changes:
Makefile
task.sh

-------------

Running tests:
Running integration tests:
[introduce-make-task 672b363] [task] Introduce task make target that runs tests before commiting the provided message
 2 files changed, 44 insertions(+)
 create mode 100755 task.sh

Note: Authors can still create normal commits. Just doing commits through make task adds the [task] prefix to the commit message that lets the reviewer know that the given commit is done through make task and represents a complete state

Release note:

New make target `task` was added for aiding in creating micro-commits

[RadaBDimitrova]

/lgtm