Attempt to merge changes from heroku before pushing new version (#4)

Why:
When trying to push changes to heroku, sometimes it gets stuck because there are some changes made from someone else besides this action which means that it needs to merge those changes to the branch its trying to push. We only want to manage deploys via this action so there's no need to be careful when pushing changes to heroku.

This addresses the issue by:
- Adding --force to git push so it is always able to deploy.

Update git config to set directory as safe (#3)

Why:

Previous configuration was breaking.

Fix action error for unsafe workspace (#2)

Update Alpine image to version 3.16 (#1)

Why:
We're using this action for a while (3 years) and it is still being built based on a outdated alpine version. A docker scan showed that it has a critical vulnerability that it's fixed on later versions.
Screenshot 2022-06-15 at 18 05 51
More info: https://security.snyk.io/vuln/SNYK-ALPINE310-APKTOOLS-1534688

Doing the same scan when using alpine:3.16 showed no known vulnerabilities.
Screenshot 2022-06-15 at 18 07 46

Also, since the action has no changes for a while, it's best if we keep doing security updates while we still use it.

This addresses the issue by:
- Update docker container alpine:3.10 to alpine:3.16 (latest ATOW)

Add git hook skipping

Fix icon and color metadata