Hotfix/change commit message length related guidelines

[morantr]

Change the limitation on the git commit subject to 72 which is the limit which passing it
will cause GitHub to wrap the line with "...":
"prefix: This is an example to a commit message subject that exceeding 72 c...
arecters"

Change the commit extended description length limitation to 100 characters. The git log looks fine
with this limitation, and since we set the code line limitation to 100, there is no reason not to
apply the same limitation on the commit message.

[adam1985d]

Change the limitation on the git commit subject to 72 which is the limit which passing it
will cause GitHub to wrap the line with "...":
"prefix: This is an example to a commit message subject that exceeding 72 c...
arecters"

Change the commit extended description length limitation to 100 characters. The git log looks fine
with this limitation, and since we set the code line limitation to 100, there is no reason not to
apply the same limitation on the commit message.

The origin of the limitations was to allow comfortable reading of commits using the "git log" (and out aliases "gitlog") in the developer shell.
If this hasn't changed - and as far as I know it didn't - your PR will break the git log prints readability.

[RanRegev]

I am fine with this change.
I think that terminals and GUIs in development environment has more than 80 chars limitations.
Setting it to 100 is fine, it also forces a strict and accurate commit subject sentence.
@adam1985d can you add a screenshot to support your concerns?

[rmelotte]

Wrapping the commit descriptions at 72-75 characters is very common across open source projects, I don't really see the benefit of switching to 100...
Commit descriptions are mostly made of sentences, not code, so to me it makes sense to have different rules for it.
Shall we also vote on that?

[itayx]

LGTM