GIT Tag task should have a force (-f) option.

We currently are unable to use this task, as we use it to tag our deployment repository plan, which we run several times against the build, usually once to test our deployment, and later on when we have release notes finalized.  As a result, the repository usually changes (release notes update), and the tagging task fails on deployment task re-runs, as the git repository tag already exists (we want the force, to move the tag forward).

We are having big problems with Bamboo trying to achieve this simple task, as even a manual tagging task fails, due to repository caching "feature".